GiteaInstall

Overview

This node interacts with the Gitea API to list forks of a specified repository. It is useful when you want to retrieve information about all the forks created from a particular repository, for example, to analyze contributions, track fork activity, or display fork details in an automation workflow.

Practical examples:

• Automatically gather and process data on all forks of a project to monitor community engagement.
• Use the list of forks to trigger further workflows, such as sending notifications when new forks are created.
• Aggregate fork metadata for reporting or analytics purposes.

Properties

Output

The node outputs JSON data representing the list of forks for the specified repository. Each item in the output array corresponds to a fork and contains details as provided by the Gitea API, such as fork metadata, owner information, and repository attributes.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• The node configuration must include the base URL of the Gitea server.
• The node uses the Gitea REST API v1 endpoints under /api/v1.

Troubleshooting

• Common issues:

  • Incorrect or missing API credentials will cause authentication failures.
  • Providing invalid repository owner or name will result in errors or empty results.
  • Pagination parameters (Page and Limit) set incorrectly may lead to unexpected or no results.

• Error messages:

  • Authentication errors typically indicate invalid or missing API tokens; verify credentials.
  • "Not Found" errors suggest the repository does not exist or the user lacks access rights.
  • Rate limiting errors may occur if too many requests are made in a short time; consider adding delays or reducing request frequency.

Links and References

• Gitea API Documentation - Repositories
• Gitea Official Website