Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node facilitates transferring a repository from one owner to another within Gitea, a self-hosted Git service. It is useful when you want to change the ownership of a repository, for example, moving a personal repository to an organization or transferring it between users. This operation ensures that the repository's data and settings are preserved while changing its ownership.

Practical examples:

  • Transferring a project repository from a personal account to a team or organization for better collaboration.
  • Moving repositories between different owners as part of organizational restructuring.

Properties

Name Meaning
Owner The current owner (user or organization) of the repository to be transferred.
Repo The name of the repository that you want to transfer.
New Owner The new owner (user or organization) who will receive ownership of the repository.
Team Ids JSON array of team IDs to add to the repository after transfer; applicable only if owned by an organization.

Output

The node outputs JSON data representing the updated repository information after the transfer operation completes successfully. This typically includes details such as the repository's new owner, name, URL, and other metadata reflecting the transfer status.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential with appropriate permissions to access and modify repositories on the Gitea instance.
  • The node communicates with the Gitea API endpoint configured via credentials, specifically targeting the /api/v1 base URL.
  • Proper network access to the Gitea server is necessary.

Troubleshooting

  • Common issues:

    • Insufficient permissions: The API token used must have rights to transfer repositories.
    • Invalid owner or repo names: Ensure the current owner and repository names are correct.
    • New owner does not exist or lacks proper setup: The target owner must be valid and able to own repositories.
    • Team IDs provided for non-organization repositories will be ignored or cause errors.
  • Error messages:

    • Authorization errors usually indicate missing or invalid API credentials.
    • Not found errors suggest incorrect owner or repository names.
    • Validation errors may occur if the new owner or team IDs are invalid.

To resolve these, verify credentials, confirm all input values, and ensure the new owner and teams exist and are properly configured.

Links and References

Discussion