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 updates an existing issue in a Forgejo repository. It allows users to modify the issue's body text, labels, and assignees by specifying the repository owner, repository name, and issue number. This is useful for managing issue details programmatically, such as updating descriptions, changing labels, or reassigning issues in automated workflows.
Use Case Examples
- Updating the description of an issue to provide more details.
- Changing the labels of an issue to reflect its current status or category.
- Assigning or reassigning users to an issue for task management.
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 update. |
| Issue Number | The unique number identifying the issue to update within the repository. |
| Body | The updated body text or description of the issue. |
| Labels | Comma-separated list of label names to assign to the issue. |
| Assignees | Comma-separated list of usernames to assign to the issue. |
Output
JSON
json- The JSON response from the Forgejo API representing the updated issue object.
Dependencies
- Forgejo API
- An API key credential for authentication
Troubleshooting
- Ensure the 'owner', 'repository', and 'issueNumber' parameters are correctly set and correspond to an existing issue.
- Labels and assignees must be provided as comma-separated strings; incorrect formatting may cause errors.
- API authentication errors may occur if the API key credential is missing or invalid.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding available endpoints and request formats.