Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node interacts with the Forgejo API to retrieve the status of a specific commit in a repository. It is useful for developers and DevOps engineers who want to programmatically check the status of a commit, such as whether it has passed CI checks or other status checks. For example, it can be used in automated workflows to monitor commit statuses and trigger subsequent actions based on the results.
Use Case Examples
- Check the status of a commit by providing the repository owner, repository name, and commit SHA.
- Integrate with CI/CD pipelines to fetch commit statuses and decide deployment steps.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository. |
| Repository | The name of the repository where the commit exists. |
| SHA | The SHA hash of the commit to get the status for. |
Output
JSON
json- The commit status information returned from the Forgejo API.
Dependencies
- Forgejo API
Troubleshooting
- Ensure the provided owner, repository, and SHA are correct and exist in the Forgejo instance.
- Check that the API credentials for Forgejo are correctly configured and have the necessary permissions.
- If the commit SHA is invalid or does not exist, the API will return an error.
- Network issues or incorrect server URL in credentials can cause request failures.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding commit status endpoints.