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 perform various operations related to tags within a repository. Specifically, the 'Tag: Get' operation retrieves information about a specific tag in a given repository owned by a specified user or organization. This is useful for workflows that need to fetch details about tags for version control, release management, or automation tasks involving repository tags.
Use Case Examples
- Retrieve details of a specific tag in a repository to automate release notes generation.
- Fetch tag information to verify the existence of a tag before deploying software.
- Use tag data to trigger CI/CD pipelines based on specific tag versions.
Properties
| Name | Meaning |
|---|---|
| Owner | The username or organization that owns the repository. |
| Repository | The name of the repository containing the tag. |
| Tag Name | The name of the tag to retrieve information for. |
Output
JSON
json- The JSON object containing the tag details retrieved from the Forgejo API.
Dependencies
- Requires an API key credential for Forgejo API authentication.
Troubleshooting
- Ensure the 'Owner', 'Repository', and 'Tag Name' fields are correctly set and correspond to existing entities in Forgejo.
- Common errors include authentication failures due to invalid or missing API credentials; verify the API key is correctly configured.
- If the tag does not exist, the API will return an error; confirm the tag name is correct and exists in the repository.
Links
- Forgejo API Documentation - Official API documentation for Forgejo, useful for understanding available endpoints and data structures.