Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with a Gitea instance to retrieve detailed information about a specific Git note attached to a commit in a repository. It is useful when you want to programmatically access metadata or annotations (notes) associated with commits in a repository hosted on Gitea.

Common scenarios include:

  • Automating retrieval of commit notes for audit or review purposes.
  • Integrating commit notes into CI/CD pipelines or reporting tools.
  • Extracting commit-related metadata for analytics or documentation generation.

For example, you can use this node to fetch the note attached to a particular commit SHA in a repository owned by a user or organization, optionally including verification details and affected files.

Properties

Name Meaning
Owner The owner of the repository (user or organization name).
Repo The name of the repository from which to get the commit note.
Sha The git reference or commit SHA identifying the specific commit whose note is retrieved.
Verification Whether to include verification information for every commit (true/false). Default: true.
Files Whether to include a list of affected files for every commit (true/false). Default: true.

Output

The node outputs JSON data representing the commit note information retrieved from the Gitea API. This includes details about the note itself, and depending on the properties set, may also include:

  • Verification details for the commit.
  • A list of files affected by the commit.

The output structure corresponds to the Gitea API response for a commit note, typically containing fields such as note content, author, timestamps, and optionally verification and file lists.

No binary data output is produced by this node.

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 of the Gitea server must be provided in the credentials configuration.

Troubleshooting

  • Invalid Owner or Repo: Ensure that the owner and repository names are correct and accessible with the provided credentials.
  • Incorrect SHA: Verify that the commit SHA or git ref exists in the repository.
  • Permission Errors: Check that the API token has sufficient permissions to read repository commit notes.
  • Network Issues: Confirm that the Gitea server URL is reachable from the n8n environment.
  • Verification or Files Disabled: Disabling verification or files options speeds up the request but omits related data; enable them if full commit detail is needed.

Common error messages will generally relate to HTTP status codes like 404 (not found), 401 (unauthorized), or 403 (forbidden). Resolving these involves checking credentials, repository existence, and access rights.

Links and References

Discussion