GiteaInstall

Overview

The node provides an operation to synchronize a repository mirror in Gitea, a self-hosted Git service. This operation is useful when you want to keep a mirrored copy of a repository up-to-date by syncing it with its remote source. Typical use cases include automating the update process of mirrors for backup, redundancy, or integration purposes.

For example, if you have a repository hosted on another platform and want to maintain a synchronized mirror in your Gitea instance, this node can trigger the sync process programmatically within an n8n workflow.

Properties

Output

The node outputs JSON data representing the result of the mirror sync operation. This typically includes details about the repository after the sync attempt, such as status information or metadata confirming the sync action.

No binary data output is indicated.

Dependencies

• Requires access 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

• Common issues:
  • Incorrect owner or repository name will cause the sync to fail.
  • Network connectivity problems to the Gitea server.
  • Insufficient permissions or invalid API token may lead to authorization errors.
• Error messages:
  • "Repository not found" indicates the specified owner/repo does not exist or is inaccessible.
  • "Unauthorized" or similar means the API token lacks required permissions.
• Resolutions:
  • Verify the owner and repo names are correct.
  • Check that the API token has appropriate scopes/permissions.
  • Ensure the Gitea server URL is reachable from the n8n environment.

Links and References

• Gitea Official Documentation
• Gitea API Reference (for mirror sync endpoint details)