Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea repository to retrieve all commits from a specified repository. It is useful for scenarios where you want to analyze commit history, audit changes, or integrate commit data into workflows such as CI/CD pipelines, reporting, or notifications.

For example, you can use this node to:

  • Fetch all commits on the master branch of a project to generate release notes.
  • Track changes made to a specific file or directory over time.
  • Collect commit metadata including verification and diff stats for auditing purposes.

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository.
Sha The SHA hash or branch name to start listing commits from (commonly "master").
Path Filepath of a file or directory to filter commits affecting that path.
Stat Whether to include diff statistics for every commit (true/false). Defaults to true.
Verification Whether to include verification information for every commit (true/false). Defaults to true.
Files Whether to include a list of affected files for every commit (true/false). Defaults to true.
Page Page number of results to return (1-based). Useful for pagination.
Limit Number of results per page (ignored if used with 'Path').
Not Commits matching this specifier will be excluded from the results.

Output

The output JSON contains an array of commit objects, each representing a single commit in the repository. Each commit object may include:

  • Commit metadata such as SHA, author, committer, message, date.
  • Diff statistics summarizing changes (if Stat is enabled).
  • Verification details about the commit signature (if Verification is enabled).
  • A list of files affected by the commit (if Files is enabled).

No binary data output is produced by this node.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL for the Gitea API must be set in the credentials.

Troubleshooting

  • Authentication errors: Ensure the API token is valid and has sufficient permissions to access the repository.
  • Invalid repository or owner: Verify that the owner and repo names are correct and accessible.
  • Pagination issues: If retrieving many commits, use the Page and Limit properties properly to paginate through results.
  • Performance considerations: Disabling Stat, Verification, or Files options can speed up responses when detailed commit info is not needed.
  • Empty results: Check if the Sha or Path filters are too restrictive or incorrect.

Links and References

Discussion