GiteaInstall

Overview

This node interacts with a Gitea server to manage repositories. Specifically, the "Repo Delete Push Mirror" operation deletes a push mirror configuration from a specified repository. This is useful when you want to stop automatically pushing changes from your Gitea repository to another remote repository configured as a push mirror.

Practical examples include:

• Removing outdated or incorrect push mirror configurations.
• Cleaning up repository settings after migrating to a different remote repository.
• Managing repository synchronization setups programmatically within an automation workflow.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the push mirror. Typically, this would confirm successful deletion or provide error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

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

Troubleshooting

• Common issues:

  • Incorrect owner or repository names can cause "not found" errors.
  • Providing a non-existent push mirror name will result in failure to delete.
  • Insufficient permissions on the API token may prevent deletion.

• Error messages and resolutions:

  • 404 Not Found: Verify that the owner, repo, and push mirror name are correct.
  • 401 Unauthorized: Check that the API token has the necessary scopes/permissions.
  • 400 Bad Request: Ensure all required parameters are provided and valid.

Links and References

• Gitea API Documentation - Repository Push Mirrors
• Gitea Official Website