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 operation lists commits associated with a specific pull request in a Forgejo repository. It is useful for developers and project managers who want to track the changes made in a pull request by viewing all commits included in it. For example, it can be used to audit code changes before merging or to review the development history of a feature branch.
Use Case Examples
- List all commits in pull request #42 of the 'my-repo' repository owned by 'my-org'.
- Fetch commits from a pull request to analyze code changes or generate reports.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository. |
| Repository | The name of the repository containing the pull request. |
| Pull Request Number | The number identifier of the pull request to list commits from. |
| Additional Options | Optional parameters to control pagination such as page number and limit of results per page. |
Output
JSON
json- ``
*sha- The SHA hash of each commit in the pull request.
*author- Author information of each commit.
*message- Commit message describing the changes.
*date- Date and time when the commit was made.
- ``
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'owner', 'repository', and 'pullRequestNumber' parameters are correctly set and correspond to existing resources in Forgejo.
- Check API credentials and server URL configuration to avoid authentication errors.
- Pagination parameters 'page' and 'limit' should be within acceptable ranges to prevent request failures.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, detailing endpoints and usage.