Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea server via its API to delete a specific tag from a repository. It is useful in scenarios where you need to programmatically manage repository tags, such as cleaning up outdated or incorrect tags, automating release workflows, or maintaining repository hygiene.

For example, if a user wants to remove a mistakenly created tag or automate the removal of tags after a certain event, this node can be integrated into an n8n workflow to perform that action without manual intervention.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the tag exists.
Repo The name of the repository from which the tag will be deleted.
Tag The name of the tag to delete from the repository.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the tag. Typically, for a delete operation, the output may be empty or contain status information confirming the deletion. No binary data output is expected.

Dependencies

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

Troubleshooting

  • Common issues:

    • Incorrect owner, repo, or tag names will cause the API call to fail.
    • Insufficient permissions or invalid API token will result in authorization errors.
    • Network connectivity problems to the Gitea server can prevent the request from completing.
  • Error messages and resolutions:

    • 404 Not Found: The specified repository or tag does not exist. Verify the owner, repo, and tag values.
    • 401 Unauthorized: Authentication failed. Check the API token and ensure it has the necessary permissions.
    • 500 Internal Server Error: Server-side issue; retry later or check Gitea server health.

Links and References

Discussion