For developers new to submodules (notes/usability-plan.md, D32):
- x and X read "restore to pin" and "restore committed pins"
- problems only, filter and fetch are shown in the footer
- ? shows every key in titled columns, then a legend of the status
words, symbols and spine roles; esc closes it
- u reads "pull (fast-forward)" on the superproject
- the detail pane suggests f when the last fetch is old
- a hint above the footer until the first key
- the header says "staged", like the tree
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ref of a pin was the closest branch containing it, so a pin on a
feature branch looked like a perfect one, and the ref changed with the
branch checked out in the submodule. Split it in two:
- Pin.Target is the branch the pin should be on: `branch =` of
.gitmodules (none if it does not exist locally), else the remote's
default branch.
- Pin.Ref is shown: the target if the pin is on it, else the branch
containing the pin with the fewest commits after it. A tie goes to the
upstream of the checked-out branch, then to the first name; no branch is
a favorite.
A pushed pin that is not on its target is `off target`, a new issue at the
new level Info (blue), counted in the header and below collapsed rows. The
spine shows the target's tip, labelled with its branch name, so the
distance from it is visible; a diverged one is the fork. The role words in
a spine label are styled separately and `you` is bold.
Add Status.TargetTip, TargetDrift and Bases.Target, Pin.Target and
Pin.Branches; drop RefSource.IsTarget. The detail pane's label column is 11
wide for the word `off target`.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Replace the Pinned/Checkout/Tip rows and the list of commits between pin
and tip with one line of history, newest on top: a node per commit with
its roles (pin, tip, you, staged, HEAD) and the number of commits between
two nodes. A staged pin shows the committed pin as its own node and notes
when it moves back. All three on one commit read "in sync".
Add Status.Drift, Committed and CommittedDrift and Status.Spine(); drop
Status.Between and Repo.FetchedAt. The fetch age moves from the header to
the detail pane (right-aligned in the name's line). The header summary is
right-aligned, ordered by importance and cut with an ellipsis if too narrow.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The header stands for the root repository: it is selected on startup,
shows the root's own state word, and the detail pane shows its state
like a submodule's (HEAD vs. upstream, changes, unpushed, leftover
submodule clones as untracked repositories). Submodules are ignored in
the root's changes; their rows show them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- On startup, after the local state is shown, fetch the superproject and
every initialized submodule (all remotes, prune, at most 8 at once).
Fetches never prompt; failures show git's message. --no-fetch skips it,
f fetches again.
- The header shows "fetching n/m", then the fetch age and failures; the
detail pane shows each submodule's last fetch and fetch errors.
- The git provider polls each repository's metadata (refs, HEAD, index,
.gitmodules) every 2 s and reports changes. The app reloads only what
changed, keeping old values, expansion and cursor; loads are
single-flight with coalesced reruns. Refresh is driven by the
repositories, so a fetch in another shell updates the view like ours.
- r reloads everything (worktree edits are not watched).
- Docs: F50-F53, N1/N8 rewritten, D18-D20 (D12 superseded).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bubble Tea prototype for browsing repositories with many nested git
submodules: collapsible tree, pins shown as ref + distance, summarized
issue words with severity levels, detail pane, async loading via a
Provider interface backed by mock data. Includes docs/ with
requirements, state model, UX guide, architecture and decision log,
plus AGENTS.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
simonfrankenandClaude Opus 5.5