gitlisted

# Git hosting operations ## Goal Route Git hosting operations (remotes, pull requests, issues, repositories) to the correct host and CLI. The primary host is the self-hosted Forgejo instance `git.starintel.actor`, used through `tea`. GitHub is only a fallback. ## Host routing 1. Determine the host from the repository remote URL (`git remote -v`): - `git.starintel.actor` (SSH or HTTPS) -> Forgejo host, use `tea`. - `github.com` -> GitHub fallback, use `gh`. - No remote or another host -> ask which host to target before creating anything remote. 2. If no remote exists yet, prefer creating or linking the repository on `git.starintel.actor`. Only use GitHub when the operator explicitly asks for GitHub or the Forgejo host is unavailable. 3. Never duplicate a repository or pull request across hosts. Pick one host per artifact and state the choice. ## CLI equivalents | Operation | Forgejo (`tea`) | GitHub fallback (`gh`) | |------------------|----------------------------------|-------------------------------| | Auth status | `tea login list` | `gh auth status` | | Login | `tea login add` | `gh auth login` | | Repo view | `tea repo view OWNER/NAME` | `gh repo view OWNER/NAME` | | Repo create | `tea repo create NAME` | `gh repo create` | | Repo search | `tea repos search NAME` | `gh repo