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 operations related to pull requests in a repository. Specifically, the 'Get' operation retrieves detailed information about a specific pull request identified by its number within a given repository owned by a user or organization. This is useful for workflows that need to fetch pull request details for review, automation, or integration purposes.
Use Case Examples
- Retrieve details of a pull request to automate code review processes.
- Fetch pull request information to trigger notifications or updates in project management tools.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository containing the pull request. |
| Repository | The name of the repository where the pull request exists. |
| Pull Request Number | The unique number identifying the pull request to retrieve. |
Output
JSON
json- The JSON object containing detailed information about the specified pull request, including metadata such as title, body, state, assignees, and other pull request attributes.
Dependencies
- Forgejo API
Troubleshooting
- Ensure that the 'Owner', 'Repository', and 'Pull Request Number' fields are correctly set and correspond to an existing pull request in the Forgejo instance.
- Verify that the API credentials for Forgejo are correctly configured and have sufficient permissions to access pull request data.
- Common errors include '404 Not Found' if the pull request does not exist or '401 Unauthorized' if authentication fails. Check the API token and repository access rights.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding available endpoints and data structures related to pull requests.