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 within a repository. Specifically, the 'Commit' resource with the 'List' operation allows users to retrieve a list of commits from a specified repository. This is useful for scenarios where you want to analyze commit history, track changes, or integrate commit data into workflows. For example, you might use this node to fetch recent commits for a project to generate reports or trigger actions based on commit activity.
Use Case Examples
- Listing all commits in a repository to monitor recent changes.
- Fetching commits to analyze contribution patterns over time.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository from which commits are to be listed. |
| Repository | The name of the repository from which commits are to be listed. |
| Additional Options | Optional parameters to control pagination such as page number and limit of results per page. |
Output
JSON
json- ``
*sha- SHA hash of the commit.
*author- Author information of the commit.
*message- Commit message describing the changes.
*date- Date and time when the commit was made.
- ``
Dependencies
- Forgejo API
Troubleshooting
- Ensure that the 'owner' and 'repository' parameters are correctly specified; incorrect values will result in API errors.
- Pagination parameters 'page' and 'limit' should be set within server limits to avoid incomplete data or errors.
- Authentication with Forgejo API must be correctly configured; missing or invalid credentials will cause request failures.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, detailing endpoints and usage.