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 a repository. Specifically, the 'Reopen' operation allows users to reopen a previously closed pull request by changing its state to 'open'. This is useful in scenarios where a pull request was closed prematurely or needs further work and review. For example, a developer can use this node to programmatically reopen a pull request after addressing review comments or fixing issues.
Use Case Examples
- Reopen a pull request that was closed by mistake to continue the review process.
- Automate reopening of pull requests based on external triggers or conditions in a CI/CD pipeline.
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 be reopened. |
Output
JSON
json- The JSON response from the Forgejo API representing the reopened pull request details.
Dependencies
- Forgejo API authentication credentials (API key or token)
Troubleshooting
- Ensure the provided owner, repository, and pull request number are correct and exist in the Forgejo instance.
- Verify that the API credentials have sufficient permissions to modify pull requests in the repository.
- Common error messages may include authorization errors if credentials are invalid or insufficient, or not found errors if the pull request does not exist. Double-check input parameters and credentials to resolve these issues.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding the pull request endpoints and parameters.