Actions73
- Repository Actions
- Issue Actions
- Pull Request Actions
- User Actions
- Organization Actions
- Release Actions
- Webhook Actions
- Branch Actions
- Commit Actions
- Tag Actions
Overview
This node interacts with the Forgejo API to manage tags within repositories. Specifically, the 'Tag: Delete' operation allows users to delete a tag from a specified repository owned by a user or organization. This is useful for repository maintenance, such as removing outdated or incorrect tags. For example, a user can automate the deletion of a tag named 'v1.0' from their project repository to keep the tag list clean.
Use Case Examples
- Deleting a tag named 'release-2023' from a repository owned by 'exampleUser' to remove an obsolete release tag.
- Automating tag cleanup in a CI/CD pipeline by deleting tags after deployment.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization name that owns the repository where the tag exists. |
| Repository | The name of the repository from which the tag will be deleted. |
| Tag Name | The name of the tag to delete from the repository. |
Output
JSON
json- The JSON response from the Forgejo API after attempting to delete the tag, indicating success or failure.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Tag Name' fields are correctly specified; incorrect values will cause the API call to fail.
- The node requires valid Forgejo API credentials; authentication errors indicate missing or invalid credentials.
- If the tag does not exist, the API will return an error; verify the tag name before attempting deletion.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding tag management endpoints.