gittop 2026.08.0

First release. gittop is a btop-inspired terminal dashboard for Git: the local repository first, so
it is useful with no network and no account, plus GitHub and GitLab panels when there is one.

Ten views

Reached with the number keys, tab, or the mouse.

• Status — the working tree in two columns: staged, unstaged, untracked and conflicted files
  beside a sidecar carrying the branch, its ahead/behind counts and recent commits. Stage, unstage,
  discard and commit from here.
• History — the commit log with a lane gutter, and an activity heatmap over the last thirteen
  weeks.
• Branches — local and remote branches with their upstream and ahead/behind.
• Graph — a braille area chart over the whole commit timeline, pannable, with selectable
  bucketing.
• Diff — the staged or unstaged diff, or a commit's, with per-file jumps.
• Stashes — save, apply, pop and drop.
• Remote — the repository as the provider describes it: stars, forks, issues, default branch,
  and where the token came from.
• CI — GitHub Actions runs and GitLab pipelines for the current branch, with a job drill-down
  on enter and a refresh interval that stops itself when anonymous or when the API budget runs
  low, and says which it is doing.
• Pull requests — open pull requests and merge requests, with a detail pane.
• Settings — one page for connecting an account, switching remote, and everything under
  [theme] and [layout] that used to mean editing a file.

Working with a repository

• Stage, unstage, discard, and commit — including during a merge, where every parent is written.
• Fetch, pull and push on a worker thread with a live progress overlay that can be cancelled.
  Pull fast-forwards or refuses; push never forces, asks first, and reports a server-side rejection
  instead of the success libgit2 reports for one.
• Interrupted rebases, merges and cherry-picks are detected and explained, with continue and abort.
• ssh key passphrases are prompted for and served to ssh over a unix socket in a private
  directory — never argv, the environment, or a file. gittop honours your own ~/.ssh/config,
  agent and known_hosts, because it runs the system ssh rather than reimplementing it.

Signing in

L opens one overlay with two routes: the OAuth 2.0 device grant (RFC 8628) where the host has a
client application configured, and a guided personal access token where it does not. Tokens are
written to the config at 0600. An environment variable always wins over a saved token, and a
sign-in that could not be saved keeps working for the session and says it will not survive a
restart.

Appearance and input

• Eight themes, including accessible — a palette whose four file states are separated by
  lightness as well as hue and stay distinct under deuteranopia, protanopia and tritanopia.
  Every status is drawn as a glyph and a letter as well as a colour, so none of them depends on
  colour to be read.
• Three glyph sets — ascii, unicode and nerd. Detection never picks nerd: there is no way
  to ask a terminal whether its font has the icons, so it is opt-in.
• Truecolor, 256-colour, 16-colour and monochrome, detected or pinned.
• Reduced motion, which makes every animation snap to its final state rather than removing it —
  a running CI row keeps its glyph and its tint, just a still one.
• Rebindable keys, a configurable tab set, a / filter over whichever list is on screen, and
  full mouse support including the wheel and clickable tabs.

Configuration

$XDG_CONFIG_HOME/gittop/config.toml, overridden by $GITTOP_CONFIG and then by --config.
--init-config writes a commented starter file. Per-host settings are table keys, so a self-hosted
GitLab or GitHub Enterprise instance is configured rather than patched. Every rejected line is
reported by name.

Known limits

• Built and tested on Linux.
• No OAuth client application is compiled in, so signing in uses the personal access token route
  unless a client_id is configured for the host. This is a packaging decision, not a missing
  feature — the token route is a first-class path.
• Saving from the settings page regenerates the config file, which drops the comments out of a
  hand-written one. The starter file says so.
• There is no test suite yet; verification is done by driving the TUI and reading rendered frames.