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 pull requests in a repository. Specifically, the 'List Files' operation retrieves the list of files changed in a specified pull request. This is useful for developers and project managers who want to review or analyze the files involved in a pull request, for example, to automate code review processes or generate reports on changes.
Use Case Examples
- Listing files changed in a pull request to automate code review workflows.
- Fetching pull request files to generate a summary of changes for project documentation.
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 whose files are to be listed. |
| Additional Options | Optional parameters to control pagination such as page number and limit of results per page. |
Output
JSON
json- Array of file objects representing files changed in the pull request.
Dependencies
- Forgejo API authentication credentials
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Pull Request Number' parameters are correctly set to valid values; otherwise, the API call will fail.
- Pagination parameters 'Page' and 'Limit' should be set within the server's allowed limits to avoid errors or incomplete data.
- Common errors include authentication failures if the API credentials are missing or invalid, and HTTP errors if the pull request does not exist or the repository is private without proper access.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, detailing endpoints including pull request file listing.