Getting started
Five minutes from install to a full inventory of your repositories.
1. Install gman
2. Connect your GitHub account
gman talks to GitHub with a token. It looks for one in this order:
- The
--tokenflag on any command - The
GITHUB_TOKENenvironment variable - The GitHub CLI — if you've ever run
gh auth login, gman uses that token automatically
Already use the gh CLI? You're done — skip to step 3.
Otherwise, the quickest route is:
…or create a personal access token at github.com/settings/tokens and export it:
Least privilege
If you'd rather grant gman only what it needs — say, read-only access — create a fine-grained token instead. Tokens & permissions has copy-paste permission recipes for read-only, dashboard, and full management tiers.
3. Take it for a spin
gman auth # what can my token do?
gman list # every repo you own, newest first
gman tui # the interactive table
gman auth prints a feature-availability table so you know up front which
gman features your token unlocks. Anything unavailable shows a hint telling
you exactly which permission it needs.
4. A first housekeeping pass
A typical first session in the TUI:
gman tui- Type
/and filter for something liketestordemo. - Move to a suspicious repo and press
Enter— check its description, last CI run, and open items. Pressvto skim its README. - Press
dto delete it. gman warns you if it has stars, forks, or is pinned to your profile, and offers to download a backup tarball first. - Press
Esc, clear the filter, and pressspaceon a few repos that just need tidying — thenb→ Delete branch on merge → ON to fix them all in one pass.
Working with GitHub Enterprise
Point gman at a GitHub Enterprise Server instance with --api-url or the
GITHUB_API_URL environment variable:
Where next?
- Commands — the full CLI reference
- The TUI — every key, screen, and workflow
- Tokens & permissions — least-privilege token recipes