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 manage pull requests within repositories. Specifically, the 'List' operation for the 'Pull Request' resource retrieves a list of pull requests from a specified repository owned by a user or organization. It supports filtering by the state of pull requests (open, closed, or all) and allows pagination through additional options such as page number and limit per page. This node is useful for automating workflows that require monitoring or processing multiple pull requests, such as generating reports, triggering CI/CD pipelines, or integrating with other tools.
Use Case Examples
- List all open pull requests in a repository to monitor active development work.
- Retrieve closed pull requests to analyze merged or rejected changes.
- Paginate through pull requests to process them in batches for bulk operations or reporting.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository from which to list pull requests. |
| State | Filter pull requests by their state: open, closed, or all. |
| Additional Options | Optional parameters to control pagination, including the page number to start from and the maximum number of results per page. |
Output
JSON
json- An array of pull request objects returned from the Forgejo API, each representing a pull request with its details such as title, state, author, and other metadata.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner' and 'Repository' parameters are correctly set to valid values; otherwise, the API may return errors or empty results.
- If pagination parameters are set incorrectly, the node might return incomplete data or no data at all. Adjust 'Page' and 'Limit' values accordingly.
- API rate limits or authentication issues can cause request failures. Verify that the API key credential is valid and has sufficient permissions.