GitHub tracker
Issues via the gh CLI. Zero API tokens to manage — gh auth login handles it.
Slot:
tracker · Name: githubmacOSSupported
LinuxSupported
WindowsSupported
The default tracker. Uses the gh CLI for everything, so you never paste a PAT into AO.
Setup
gh auth loginPick GitHub.com → HTTPS → Login with a web browser. Then:
tracker: github
projects:
myproject:
repo: owner/reporepo must be owner/name (not a URL) — it's what gh expects.
How it's used
| Operation | gh command invoked |
|---|---|
| Fetch issue | gh issue view <num> --json title,body,... |
| Create issue | gh issue create |
| Comment on issue | gh issue comment |
| Close issue | gh issue close |
| List issues | gh issue list |
Config
No plugin-level config keys. The github tracker doesn't need anything beyond your gh auth.
Troubleshooting
gh: authentication required— rungh auth login.could not resolve to an Issue— the issue number is wrong, orrepodoesn't match the project.- Rate limits — AO batches and paces issue lookups, but heavy bursts can still hit limits.
ghreports them clearly in logs.