GiteaInstall

Overview

This node integrates with the Gitea API to perform repository-related operations. Specifically, the "Repo Push Mirror Sync" operation triggers a synchronization of a mirrored repository by pushing updates from the source repository to its mirror. This is useful in scenarios where you maintain mirrors of repositories and want to ensure they are up-to-date automatically.

Practical examples include:

• Keeping a backup mirror repository synchronized with the main repository.
• Synchronizing code between different hosting services via Gitea mirrors.
• Automating repository mirroring workflows within CI/CD pipelines.

Properties

Output

The node outputs JSON data representing the result of the mirror sync operation. Typically, this includes status information about the synchronization process, such as success confirmation or error details if the sync failed.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• Needs the base URL of the Gitea server configured in the credentials.
• Depends on the Gitea API being accessible and the user having appropriate permissions to trigger mirror syncs on the specified repository.

Troubleshooting

• Common issues:

  • Incorrect owner or repository name leading to "not found" errors.
  • Insufficient permissions to trigger mirror sync on the repository.
  • Network connectivity problems preventing access to the Gitea API.
  • Invalid or expired API authentication token.

• Error messages and resolutions:

  • "Repository not found": Verify that the owner and repo names are correct and that the repository exists.
  • "Unauthorized" or "Forbidden": Check that the API key has sufficient permissions.
  • Timeout or network errors: Ensure the Gitea server URL is reachable and there are no firewall restrictions.

Links and References

• Gitea API Documentation
• Gitea Repository Mirroring Guide
• n8n Documentation on Creating Custom Nodes