drydock
What's uncommitted, unpushed, and unreleased across every repo you own. A live TUI dashboard for a fleet of git repos. | | | | | | / | '| | | |/ |/ \ / | |/ / segment below a root — so point drydock at $GHQROOT and every repo lands in a github.com group, or point it a level deeper and the groups are the owners, which is usually what you want.
yetidevworks · Terminal & CLI
- Tier 1 — refs, tags, tracking counts, stash count, in-progress operations
- Tier 2 — the working-tree scan — is cached against HEAD and the index
- A filesystem watcher then re-probes individual repos as they change, which
- • NeutralGitHub Issue
Work with `ghq` out of the box
“Seems like this would work well in tandem with [ghq]( and its `GHQ_ROOT` environment variable.”
- ↑ PositiveGitHub Issue
JJ support
“This would be awesome, but I generally use [JJ]( which means most of my repos have detached HEAD states and such. So I'm not quite sure it would work well there. Any thoughts on this? If you haven't used JJ before then the problems are probably not really on your radar - there's…”