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 perform various operations related to commits in a repository. Specifically, the 'Commit' resource with the 'Get' operation allows users to retrieve commit information from a specified repository. Users can fetch details of a specific commit by providing its SHA hash or get the latest commit from the default branch if the SHA is not provided. This node is useful for scenarios where you need to track changes, audit commit history, or integrate commit data into workflows, such as triggering actions based on commit details or displaying commit information in dashboards.
Use Case Examples
- Fetch the latest commit from the default branch of a repository to monitor recent changes.
- Retrieve a specific commit by its SHA to analyze the changes introduced in that commit.
- Integrate commit data into a CI/CD pipeline to trigger builds or deployments based on commit details.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository. This is required to identify the repository's owner. |
| Repository | The name of the repository from which to get the commit information. This is required to specify the target repository. |
| SHA | The SHA hash of the commit to retrieve. If left empty, the node fetches the latest commit from the default branch. This property is optional. |
Output
JSON
json- The JSON object containing commit details returned from the Forgejo API. This includes commit metadata such as author, message, date, and other commit-specific information.
Dependencies
- Requires an API key credential for Forgejo API authentication, including the server URL for the Forgejo instance.
Troubleshooting
- Ensure that the 'Owner' and 'Repository' fields are correctly specified to avoid 'Not Found' errors.
- If specifying a SHA, verify that the SHA is valid and exists in the repository to prevent errors.
- Check API credentials and server URL configuration if authentication errors occur.
- Handle pagination if retrieving multiple commits in other operations, although 'Get' for a single commit typically does not paginate.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding commit-related endpoints and parameters.