​

GitHub Enterprise Hosts

​

Accepted Host Inputs

• bare hostnames like github.example.com
• full web URLs like https://github.example.com
• explicit API roots like https://github.example.com/api/v3
• localhost-style API roots for tests like http://127.0.0.1:8787/api/v3

gitquarry --host github.example.com auth login
gitquarry --host https://github.example.com search "internal platform"
gitquarry --host https://github.example.com/api/v3 inspect org/repo

​

Normalization Rules

• a canonical web host used for credential lookup
• a canonical API base used for HTTP requests

• github.com
• www.github.com
• api.github.com

• web host: github.com
• API base: https://api.github.com

​

Host-Scoped Auth

• logging into GitHub.com does not log you into GitHub Enterprise
• each host can have a different PAT
• auth status and auth logout are host-aware

gitquarry --host github.com auth status
gitquarry --host https://ghe.example.com auth login
gitquarry --host https://ghe.example.com auth status

​

Host-Specific Environment Variables

GITQUARRY_TOKEN_<NORMALIZED_HOST>

export GITQUARRY_TOKEN_GITHUB_COM=ghp_example
export GITQUARRY_TOKEN_GIT_EXAMPLE_COM=ghp_example
export GITQUARRY_TOKEN_127_0_0_1_8787=ghp_example

1. host-specific env var
2. global GITQUARRY_TOKEN
3. saved secure credential
4. explicit insecure-file fallback

​

Good Enterprise Workflow

gitquarry --host https://ghe.example.com auth login
gitquarry --host https://ghe.example.com search "platform tooling" --org engineering
gitquarry --host https://ghe.example.com inspect engineering/internal-cli

​

Common Mistakes

• Passing an empty --host value. That fails with E_HOST_INVALID.
• Assuming GitHub.com credentials automatically apply to GitHub Enterprise.
• Mixing web hosts and API bases mentally. Gitquarry normalizes them, but auth is keyed to the normalized web host.
• Expecting device flow or browser login. v1 is PAT-only.