Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve information about a specific tag in a repository. It is useful when you want to programmatically access metadata or details about a particular tag within a Git repository hosted on a Gitea instance. Common scenarios include automation workflows that need to check release tags, validate versioning, or trigger actions based on tag data.

For example, you might use this node to:

  • Fetch details of a release tag before deploying software.
  • Verify if a certain tag exists in a repository as part of a CI/CD pipeline.
  • Extract tag metadata for reporting or auditing purposes.

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository.
Tag The name of the tag to retrieve information about.

Output

The node outputs JSON data representing the details of the specified tag from the repository. This typically includes metadata such as the tag name, commit SHA it points to, message, author, and other relevant tag information as provided by the Gitea API.

If the node supports binary data output (not evident from the code snippet), it would represent any associated binary content related to the tag, but here the focus is on JSON metadata.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the credentials.
  • Uses the @devlikeapro/n8n-openapi-node package internally to build properties and handle API interactions.

Troubleshooting

  • Common issues:
    • Incorrect owner, repo, or tag names will result in errors or empty responses.
    • Authentication failures due to invalid or missing API tokens.
    • Network connectivity problems to the Gitea server.
  • Error messages:
    • "Not Found" or similar HTTP 404 errors indicate the tag or repository does not exist or is inaccessible.
    • "Unauthorized" or HTTP 401 errors suggest issues with API credentials.
  • Resolutions:
    • Double-check input property values for typos.
    • Verify API credentials and permissions.
    • Ensure the Gitea server URL is reachable from the n8n environment.

Links and References

Discussion