Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to perform administrative actions on repositories. Specifically, the "Admin Delete Unadopted Repository" operation allows an administrator to delete a repository that is unadopted (i.e., not currently maintained or linked to an active user). This can be useful for cleaning up unused or orphaned repositories in an organization or instance.

Practical examples include:

  • Automatically removing stale or abandoned repositories to maintain a clean repository list.
  • Managing repository lifecycle by deleting repos that no longer have an owner or maintainer.

Properties

Name Meaning
Owner The username or organization name that owns the repository to be deleted.
Repo The name of the repository to delete.

Both properties are required inputs to specify exactly which repository should be deleted.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the specified repository. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

No binary data output is involved.

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 REST API being accessible and the authenticated user having admin permissions to delete repositories.

Troubleshooting

  • Common issues:

    • Insufficient permissions: The API token must have admin rights to delete repositories.
    • Incorrect owner or repo names: Typos or wrong values will cause the API call to fail.
    • Network or connectivity problems with the Gitea server.
  • Error messages:

    • Authorization errors indicating lack of permission — ensure the API key has admin privileges.
    • Not found errors if the specified repository does not exist under the given owner.
    • Validation errors if required parameters are missing or invalid.

Resolving these typically involves verifying credentials, checking input property values, and ensuring network access to the Gitea API.

Links and References

Discussion