Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to edit an existing label within a specified organization. It is useful when you want to update the attributes of a label such as its name, color, description, or status flags like whether it is archived or exclusive. Typical use cases include managing project labels dynamically in an organization’s repository or issue tracker, ensuring labels remain relevant and up-to-date.

For example, if your team uses labels to categorize issues or pull requests, you might want to rename a label, change its color for better visibility, or archive labels that are no longer in use.

Properties

Name Meaning
Org The name of the organization where the label exists.
Id The unique identifier of the label to be edited.
Color The new color code (e.g., #00aabb) to assign to the label.
Description A textual description providing more details about the label.
Exclusive A boolean flag indicating if the label is exclusive (true or false).
Is Archived A boolean flag indicating if the label should be marked as archived (true or false).
Name The new name to assign to the label.

Output

The node outputs JSON data representing the updated label object after the edit operation completes successfully. This JSON typically includes all label properties such as id, name, color, description, exclusivity, and archival status reflecting the changes made.

If the node supports binary data output, it would generally relate to file attachments or images associated with the label, but this operation focuses on label metadata only, so no binary output is expected.

Dependencies

  • Requires an API key credential for authenticating with the Gitea API.
  • Needs the base URL of the Gitea instance configured in the credentials.
  • The node depends on the Gitea REST API v1 endpoints to perform label updates within organizations.

Troubleshooting

  • Invalid Organization or Label ID: If the organization name or label ID does not exist, the API will return an error. Verify these values before running the node.
  • Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to edit labels in the target organization.
  • Invalid Color Format: The color property should be a valid hex color code; otherwise, the API may reject the request.
  • Missing Required Fields: Both "Org" and "Id" are required. Omitting them will cause the node to fail.
  • API Rate Limits: Frequent edits may hit API rate limits; handle errors accordingly.

Links and References

Discussion