docs(settings): describe the GitHub integration as the local gh CLI login, not OAuth (#26609)

Orca has no OAuth app; it reads tokens from the gh CLI on the machine running
Orca. Document that, the per-host login for Remote Orca Servers, and the
repo/read:org/project scopes auth-diagnose expects.

Refs #26604

Co-authored-by: Neil <4138956+nwparker@users.noreply.github.com>
This commit is contained in:
eatmoreduck
2026-10-26 04:22:49 -07:00
committed by GitHub
co-authored by Neil
parent e50fe1e10e
commit 15fc7a6769
+1 -1
View File
@@ -87,7 +87,7 @@ Settings are grouped into panes. Everything here is searchable with `Cmd-,` then
## Integrations
- GitHub OAuth.
- GitHub — uses the `gh` CLI login on the machine running Orca (on a [Remote Orca Server](/docs/remote-servers), run `gh auth login` on the server); there is no Orca OAuth app to approve or revoke. Expects the `repo`, `read:org`, and `project` scopes. See [Troubleshooting GitHub errors](/docs/github-errors).
- Linear API token.
- Jira — Cloud (email + API token) or self-hosted Server/Data Center (PAT or username/password). See [Jira items drawer](/docs/review/jira).
- Bitbucket Cloud — **Connect** with **Email & API token** (default) or an **Access token**. Orca verifies the credential before saving. `ORCA_BITBUCKET_*` environment variables take precedence and hide Connect / Disconnect. Saved credentials stay on this machine — on a [Remote Orca Server](/docs/remote-servers), set the env vars on the server instead. See [Hosted reviews](/docs/review/github).