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 operation reopens a previously closed issue in a specified repository on Forgejo. It is useful in scenarios where an issue was closed prematurely or needs to be revisited. For example, if a bug report was closed but the problem persists, this operation can reopen the issue to continue tracking and resolving it.
Use Case Examples
- Reopen a closed issue in a project repository to resume work on it.
- Automatically reopen issues based on certain workflow triggers or conditions.
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 reopened. |
| Issue Number | The unique number identifying the issue to reopen within the repository. |
Output
JSON
json- The JSON response from the Forgejo API representing the reopened issue's details.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the provided owner, repository, and issue number are correct and the issue is currently closed; otherwise, reopening may fail.
- Check that the API credentials have sufficient permissions to modify issues in the repository.
- Common error messages may include authorization errors if credentials are invalid or permission errors if the user lacks rights to reopen issues. Verify credentials and repository access rights.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, including issue management endpoints.