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 allows adding a comment to an existing issue in a Forgejo repository. It is useful for automating issue tracking workflows by programmatically appending comments to issues, such as providing updates, feedback, or additional information. For example, it can be used in CI/CD pipelines to comment on issues when certain events occur or to notify team members about issue status changes.
Use Case Examples
- Adding a comment to an issue to provide status updates.
- Automating feedback on issues based on external triggers.
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. |
| Issue Number | The unique number identifying the issue to which the comment will be added. |
| Body | The content of the comment to add to the issue. |
Output
JSON
jsonid- ID of the created commentbody- Content of the commentuser- User who created the commentcreated_at- Timestamp when the comment was createdupdated_at- Timestamp when the comment was last updated
Dependencies
- Forgejo API
Troubleshooting
- Ensure the provided repository owner and name are correct and accessible with the provided API credentials.
- Verify that the issue number exists in the specified repository.
- Check that the API credentials have permission to add comments to issues in the repository.
- Common error messages may include authentication errors, permission denied, or issue not found. Verify credentials and input parameters to resolve these.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, detailing endpoints and usage.