Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves the combined status for a specific reference (branch, tag, or commit) in a repository hosted on a Gitea instance. The combined status aggregates the statuses of all commits associated with the given ref, which is useful for understanding the overall state of continuous integration checks, build results, or other status indicators related to that ref.

Common scenarios include:

  • Monitoring the health of a branch before merging.
  • Checking the status of a specific commit or tag to ensure it passed all required checks.
  • Automating deployment pipelines by verifying combined statuses programmatically.

For example, you might use this node to fetch the combined status of the main branch in your repository to decide whether it is safe to deploy the latest changes.

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository.
Ref The name of the branch, tag, or commit SHA for which to get the combined status.
Page (Optional) The page number of results to return (1-based). Useful for paginated results.
Limit (Optional) The number of results per page to return.

Output

The node outputs JSON data representing the combined status of the specified ref in the repository. This typically includes:

  • Overall state of the combined status (e.g., success, failure, pending).
  • Details about individual statuses contributing to the combined status, such as context names, descriptions, states, and target URLs.
  • Metadata like the total count of statuses and pagination info if applicable.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential to authenticate with the Gitea instance.
  • The node expects the base URL of the Gitea server to be configured in the credentials.
  • Network access to the Gitea API endpoint /api/v1/repos/{owner}/{repo}/statuses/{ref}/combined is necessary.

Troubleshooting

  • Invalid Owner/Repo/Ref: If the specified owner, repository, or ref does not exist, the API will return an error. Verify these inputs carefully.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to access repository statuses.
  • Pagination Issues: If many statuses exist, use the Page and Limit properties to paginate through results properly.
  • Network Connectivity: Confirm that the n8n instance can reach the Gitea server URL configured in credentials.

Links and References

Discussion