Remove “Adopt Repository” from Gitea UI and Backend, Implement Equivalent in tea CLI

[lunny]

Feature Description

We propose removing the “Adopt Repository” feature from the Gitea web UI and backend, while introducing a similar capability in the tea command-line tool.

Rationale

• The feature is rarely used via the web UI and adds unnecessary complexity to the Gitea core codebase.
• Moving this functionality to the tea CLI keeps the Gitea UI simpler and more user-friendly, while still providing advanced users with the same capability.
• This change aligns with the goal of keeping the web interface focused on common workflows and moving niche or administrative actions to CLI tooling.

Proposed Changes:

Gitea Backend/UI

• Remove all backend logic, API endpoints to adopting repositories.
• Remove the corresponding UI components.
• Update documentation and translations accordingly.

tea CLI

• Add a new command (e.g., tea repo adopt) to provide equivalent repository adoption functionality.
• Support the same validation and permission checks as the original feature.
• Ensure proper error handling and user feedback in CLI output.

Screenshots

No response

[karthikbhandary2]

I think it’s better to keep the API available. If needed, we can remove it from the UI, but retaining it as an API would still provide flexibility. Just sharing my opinion here.

[TheFox0x7]

Don't you mean gitea CLI? AFAIK tea relies on API do adopting a repository without an API endpoint for it would be impossible.
Unless I'm misunderstanding the idea. Adopting repositories was a feature for when gitea looses track of a repo that's already in gitea's storage was it not? At least that's the main usecase I saw around

[karthikbhandary2]

Adopting repositories was a feature for when gitea looses track of a repo that's already in gitea's storage was it not?

yes.