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 'Close' operation allows users to close an existing pull request by setting its state to 'closed'. This is useful in scenarios where a pull request is no longer needed or has been superseded, helping maintain repository hygiene and workflow management.
Use Case Examples
- Automatically close stale pull requests after a period of inactivity.
- Close a pull request programmatically after merging or rejecting changes.
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 closed. |
Output
JSON
json- The JSON response from the Forgejo API representing the updated pull request after closing it.
Dependencies
- Forgejo API
Troubleshooting
- Ensure the provided 'Owner', 'Repository', and 'Pull Request Number' are correct and the pull request exists.
- Verify that the API credentials have sufficient permissions to modify pull requests.
- Common errors include authentication failures, invalid repository or pull request identifiers, and network issues. Check API credentials and network connectivity if errors occur.
Links
- Forgejo API Documentation - Official documentation for the Forgejo API, including endpoints for managing pull requests.