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 'Delete' operation allows users to delete a pull request by specifying the repository owner, repository name, and the pull request number. This is useful for automating repository management tasks such as cleaning up obsolete or unwanted pull requests.
Use Case Examples
- Deleting a pull request after it has been merged or closed to keep the repository clean.
- Automating the removal of pull requests that do not meet contribution guidelines.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository where the pull request exists. |
| Repository | The name of the repository containing the pull request to be deleted. |
| Pull Request Number | The unique number identifying the pull request to delete within the repository. |
Output
JSON
json- The JSON response from the Forgejo API after attempting to delete the pull request. Typically indicates success or failure of the deletion operation.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Pull Request Number' fields are correctly set and correspond to an existing pull request.
- If the API returns an error, verify that the API key credential has sufficient permissions to delete pull requests.
- Check network connectivity and the Forgejo server URL configuration in the credentials if requests fail to reach the API.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding available endpoints and required parameters.