Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with a Gitea server via its API, specifically to reject a repository transfer request. When a repository owner receives a transfer request for one of their repositories, they can use this operation to decline the transfer, preventing the repository from moving to the new owner.

Common scenarios include:

  • Managing repository ownership within an organization or team.
  • Automating administrative tasks related to repository transfers.
  • Integrating repository management workflows in CI/CD pipelines or project management tools.

Example: If a user mistakenly initiates a transfer of a repository to another user or organization, the current owner can programmatically reject that transfer using this node.

Properties

Name Meaning
Owner The username or identifier of the current owner of the repository to which the transfer was requested. This is required to specify whose repository transfer is being rejected.
Repo The name of the repository for which the transfer request should be rejected. This identifies the specific repository under the owner's account.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to reject the repository transfer. Typically, this will confirm whether the rejection was successful or provide error details if it 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 or key configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials leading to authorization errors.
    • Incorrect owner or repository names causing "not found" errors.
    • Network connectivity problems preventing access to the Gitea server.

  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key/token is valid and has sufficient permissions.
    • 404 Not Found: Verify that the owner and repository names are correct and that a transfer request exists.
    • 400 Bad Request: Ensure all required parameters are provided and correctly formatted.

Links and References

Discussion