Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to delete tag protection rules from a specified repository. Tag protection is a feature that restricts certain actions on tags, such as preventing deletion or modification of important tags. This operation removes such protection by deleting the tag protection rule identified by its ID.

Common scenarios for using this node include:

  • Automating repository maintenance by removing outdated or unnecessary tag protections.
  • Integrating with CI/CD pipelines to dynamically adjust tag protections based on deployment workflows.
  • Managing repository permissions programmatically in bulk operations.

Example: Automatically remove tag protection from a release tag after a successful deployment to allow further modifications.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository from which the tag protection will be deleted.
Id The numeric identifier of the protected tag rule to delete.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the tag protection. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

No binary data output is expected from this operation.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials configuration.

Troubleshooting

  • Invalid Owner or Repo: If the owner or repository name is incorrect, the API will return an error indicating the repository was not found. Verify these values carefully.
  • Invalid Id: Providing a non-existent tag protection ID will result in an error. Ensure the ID corresponds to an existing tag protection rule.
  • Authentication Errors: Missing or invalid API tokens will cause authorization failures. Confirm that the API key credential is correctly configured and has sufficient permissions.
  • Network Issues: Connectivity problems with the Gitea server can cause request failures. Check network access and server availability.

Links and References

Discussion