Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with a Gitea instance to retrieve the list of files changed in a specific pull request within a repository. It is useful for automation workflows that need to analyze or process pull request file changes, such as triggering code quality checks, generating reports on modified files, or integrating with other tools based on pull request content.

For example, you could use this node to:

  • Automatically fetch and review all files changed in a pull request before merging.
  • Trigger downstream processes only if certain types of files were modified.
  • Collect metadata about pull requests for auditing or compliance purposes.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the pull request exists.
Repo The name of the repository containing the pull request.
Index The index (number) of the pull request to retrieve files from.
Skip To Optional parameter to skip results until a specified filename is reached (pagination).
Whitespace Controls how whitespace differences are handled when listing files. Options:
- Ignore All: ignore all whitespace changes
- Ignore Change: ignore changes in amount of whitespace
- Ignore Eol: ignore end-of-line whitespace differences
- Show All: show all whitespace changes
Page The page number of results to return (1-based pagination).
Limit The maximum number of results to return per page (page size).

Output

The node outputs JSON data representing the files changed in the specified pull request. Each item typically includes details such as filename, status (added, modified, deleted), additions, deletions, and patch information describing the changes.

If binary data is present (not indicated here), it would represent file contents or diffs, but this node primarily returns structured JSON metadata about pull request files.

Dependencies

  • Requires connection to a Gitea instance via its API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

  • Invalid Owner/Repo or Pull Request Index: Ensure the owner, repo name, and pull request index are correct and exist in the Gitea instance.
  • Authentication Errors: Verify that the API key/token is valid and has sufficient permissions to access repository pull requests.
  • Pagination Issues: If many files are changed, use the Page and Limit properties to paginate through results properly.
  • Whitespace Option Misuse: Using inappropriate whitespace options might cause unexpected diff results; try different settings if output seems incorrect.

Links and References

Discussion