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 issues within repositories. Specifically, the 'Delete' operation under the 'Issue' resource allows users to delete an issue from a specified repository. This is useful for automating issue management workflows, such as removing obsolete or invalid issues programmatically.
Use Case Examples
- Automatically delete issues that are marked as duplicates or invalid in a repository.
- Integrate with other automation tools to clean up issues after certain conditions are met.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository where the issue exists. |
| Repository | The name of the repository containing the issue to be deleted. |
| Issue Number | The unique number identifying the issue to delete within the repository. |
Output
JSON
json- The JSON response from the Forgejo API after deleting the issue, typically indicating success or failure.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Issue Number' parameters are correctly set and correspond to existing entities in Forgejo.
- Common errors include authentication failures (check API credentials), permission errors (ensure the API token has rights to delete issues), and not found errors if the issue number does not exist.
- If the node fails and 'Continue On Fail' is not enabled, the workflow will stop. Enable 'Continue On Fail' to handle errors gracefully within the workflow.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding the endpoints and data structures involved in issue deletion.