Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation allows editing an existing issue in a repository hosted on a Gitea instance. It is useful for updating issue details such as title, body, assignees, milestone, due date, state, and other metadata after the issue has been created. Typical use cases include automating issue management workflows, synchronizing issue data from other systems, or programmatically adjusting issue attributes based on external events.

For example, you could use this node to:

  • Change the assignees of an issue when team members change.
  • Update the issue's milestone or due date as project timelines evolve.
  • Modify the issue's state (e.g., open, closed) based on automated testing results or deployment status.
  • Edit the issue title or description to add more context or correct information.

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 edit.
Assignee Deprecated single assignee field (string).
Assignees JSON array of usernames to assign to the issue.
Body The main content or description text of the issue.
Due Date The due date for the issue, typically in string format (e.g., ISO 8601 date).
Milestone Numeric ID of the milestone to associate with the issue.
Ref Reference string related to the issue (context-specific usage).
State The state of the issue, e.g., "open" or "closed".
Title The title or summary of the issue.
Unset Due Date Boolean flag indicating whether to remove the due date from the issue (true/false).

Output

The node outputs the updated issue data in the json output field. This typically includes all the properties of the edited issue as returned by the Gitea API, reflecting the new state after the update. The output can be used downstream in workflows to trigger further actions or logging.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid repository owner or repo name will cause the API call to fail.
    • Providing an incorrect issue index (non-existent issue number) will result in an error.
    • Malformed JSON in the assignees property may cause parsing errors.
    • Missing required fields like owner, repo, or index will prevent execution.

  • Error messages:

    • 404 Not Found: The specified issue does not exist; verify the owner, repo, and index.
    • 401 Unauthorized: Authentication failed; check API credentials.
    • 400 Bad Request: Invalid input data, such as malformed JSON or invalid field values.

  • Resolutions:

    • Double-check all required inputs for correctness.
    • Ensure the API key or token has sufficient permissions.
    • Validate JSON formatting for complex fields before running the node.

Links and References

Discussion