Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node allows users to create a comment on an existing issue within a repository hosted on a Gitea instance. It is useful for automating interactions with issues, such as adding updates, feedback, or additional information programmatically without manually accessing the Gitea web interface.

Common scenarios include:

  • Automatically posting status updates or logs to an issue when triggered by external events.
  • Adding comments from other integrated systems (e.g., CI/CD pipelines, monitoring tools).
  • Enabling bots or automation workflows to interact with issue discussions.

Example: When a build fails in a CI system, this node can add a comment to the related issue describing the failure details.

Properties

Name Meaning
Owner The owner of the repository where the issue exists.
Repo The name of the repository containing the issue.
Index The index (number) of the issue to which the comment will be added.
Body The content of the comment to post on the issue.

Output

The node outputs JSON data representing the newly created comment on the issue. This typically includes details such as the comment ID, body text, author information, creation timestamp, and any metadata returned by the Gitea API.

No binary data output is involved.

Dependencies

  • Requires access to a Gitea instance via its REST API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

  • Issue not found or invalid index: Ensure the issue index number corresponds to an existing issue in the specified repository.
  • Authentication errors: Verify that the API token or credentials are valid and have sufficient permissions to comment on issues.
  • Repository or owner incorrect: Double-check the spelling and case sensitivity of the owner and repository names.
  • API rate limits or connectivity issues: Confirm network access to the Gitea server and check for any rate limiting imposed by the API.

Links and References

Discussion