Archived
Compare pins with a target branch and flag pins off it
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>
This commit is contained in:
Claude Sonnet 5.5
+58
-1
@@ -220,7 +220,7 @@ shown in a palette in the detail pane, next to what they act on; global keys
|
||||
instead, so small terminals need no extra UI (no overlay or action menu).
|
||||
Keys never depend on what is visible.
|
||||
|
||||
## Pin resolves to the closest branch
|
||||
## Pin resolves to the closest branch (superseded by D26)
|
||||
|
||||
A pin on a pushed feature branch showed as diverged from `origin/main`,
|
||||
because `branch = main` in `.gitmodules` won before any distance was looked
|
||||
@@ -424,3 +424,60 @@ happened is what decides between a merge and a rebase. Cost: one
|
||||
Only one fork is drawn; with two diverged commits (rare) the old line with
|
||||
the diverged gap remains, since nodes on three lanes would need the
|
||||
merge bases between all of them.
|
||||
|
||||
## D26 — The ref is the target branch; a pin off it is `off target`
|
||||
|
||||
**Context.** The main use is checking that a superproject points at the right
|
||||
commits of its submodules, ideally the tips of `main`. D1's "closest branch"
|
||||
(see "Pin resolves to the closest branch") answered *where the pin is*, not
|
||||
*where it should be*: a pin on a feature branch showed that branch, `in sync`
|
||||
and quiet, because `unpushed` (D6) is satisfied by any remote branch. The
|
||||
closest branch also changed with the branch checked out in the submodule, so
|
||||
two machines could show different refs for the same superproject commit.
|
||||
**Decision.** Supersedes "Pin resolves to the closest branch". The ref is the
|
||||
target: the `branch =` of `.gitmodules` (no fallback to the default branch if
|
||||
it does not exist locally), else the remote's default branch (`HEAD`, `main`,
|
||||
`master`). Without a target the checked-out branch's upstream, a tag or the
|
||||
SHA are shown for orientation, but cannot make a pin off target. A pushed pin
|
||||
with commits its target lacks (`Ahead > 0`) is `off target`: a new issue with
|
||||
the new level `LevelInfo` (blue), listed last. The other branches that contain
|
||||
the pin are named in its text.
|
||||
**Alternatives.** Severity by the superproject's branch (strict on `main`,
|
||||
quiet elsewhere): rejected, the severity should not depend on the branch.
|
||||
Matching the superproject's branch name in submodules: rejected, feature
|
||||
branches need not be named alike. Warn level: not now; behind the target is
|
||||
quiet and `off target` is information, since a feature branch of the
|
||||
superproject legitimately pins feature commits.
|
||||
**Consequences.** `RefFromContains` and the 16-branch scan are gone;
|
||||
`Pin.Branches` replaces them. `off target` is counted in the header and below
|
||||
collapsed rows (blue `·k`) and is part of "problems only". The issue word
|
||||
needs 10 columns, so the detail pane's label column is 11 wide.
|
||||
|
||||
**Amendment (with D26): target and ref are separate.** Checking a real
|
||||
repository, a stale `branch = marco-dev` in `.gitmodules` made every pin
|
||||
"↑52↓12 from marco-dev" although the pin was on `main`, one commit behind. The
|
||||
target (`PinInfo.Target`) now only decides `off target`; the ref shown is the
|
||||
target if the pin is on it, else the branch containing the pin that is closest
|
||||
to it, with its real distance. The closest branch is the one with the fewest
|
||||
commits after the pin; ties go to the upstream of the branch the submodule is
|
||||
on, then alphabetically. The default branch is no favorite: if
|
||||
`.gitmodules` targets another branch, `main` is just another branch. The
|
||||
tie-break must be fixed, or the same superproject commit would show
|
||||
different branches on different machines. The text of the issue names both
|
||||
(`pin not on origin/marco-dev, on origin/fix/x +1`), so a stale declaration
|
||||
is visible. `RefFromContains` is back; `RefSource.IsTarget` is gone.
|
||||
|
||||
**Amendment (with D26): the target on the spine.** An `off target` row only
|
||||
said that the pin is elsewhere, not how far from the target. The target's tip
|
||||
is now a node (`target`) next to the pin, the tip of the shown ref and the
|
||||
checkout, so a feature pin reads as a distance from main. The shown ref
|
||||
contains the pin, so only the target can fork from it, and the fork code
|
||||
needs no new case. Cost: `log -1`, one `rev-list --left-right --count` and,
|
||||
if diverged, one `merge-base` per off-target submodule.
|
||||
|
||||
**Amendment (with D26): labels.** The target's tip is labelled with its short
|
||||
branch name (`marco-dev`) instead of the word `target`: it is usually short,
|
||||
and the name is what people know. Long names are cut at 16 columns, so the
|
||||
label column cannot grow without bound. In a label every role word has its
|
||||
own style, and `you` is bold in the default color: it was lost between the
|
||||
muted words, and it is the one the user looks for.
|
||||
|
||||
@@ -48,8 +48,14 @@ commit hashes. It doesn't answer the questions users actually have:
|
||||
muted `in sync`, or a blue `staged` if their pin change is staged. With
|
||||
issues, a staged pin adds a blue `●` after the word.
|
||||
See [state-model.md](state-model.md) for the full rules.
|
||||
- **F11** Each submodule shows its pin as a ref (`origin/main`, a tag, or a
|
||||
short SHA as a fallback) and the distance to that ref (`↑n`, `↓n`, `↑n↓m`).
|
||||
- **F11** Each submodule shows its pin as a ref and the distance to it
|
||||
(`↑n`, `↓n`, `↑n↓m`). The ref is the **target** branch (`branch =` of
|
||||
`.gitmodules`, else the remote's default branch) if the pin is on it, else
|
||||
the branch the pin is on that it is closest to; only without any a tag or
|
||||
a short SHA.
|
||||
- **F11a** A pin that is pushed but not on its target branch (for example
|
||||
only on a feature branch) is `off target`, an information (blue) naming
|
||||
the branch it is on. It does not depend on the superproject's branch.
|
||||
- **F12** A pin that is not reachable from any remote ref ("unpushed") is
|
||||
the most prominent state.
|
||||
- **F13** States load asynchronously per submodule; a submodule shows a
|
||||
|
||||
+54
-43
@@ -11,12 +11,13 @@ them.
|
||||
|---|---|
|
||||
| **Pinned** | The gitlink recorded in the superproject index (differs from HEAD → `PinStaged`) |
|
||||
| **Checked out** | The submodule's `HEAD` |
|
||||
| **Tip** | The tip of the ref the pin was resolved to, e.g. `origin/main` |
|
||||
| **Tip** | The tip of the ref the pin was resolved to, normally the target branch, e.g. `origin/main` |
|
||||
|
||||
This gives two independent questions:
|
||||
|
||||
- **Is the checkout on the pin?** → `off pin` if not.
|
||||
- **Where is the pin relative to its ref?** → `↑n` / `↓n` / `↑n↓m`.
|
||||
- **Where is the pin relative to its ref?** → `↑n` / `↓n` / `↑n↓m`. A pin
|
||||
that is not on its target branch (but on another) is `off target`.
|
||||
|
||||
## Raw status dimensions
|
||||
|
||||
@@ -32,7 +33,8 @@ in several at once.
|
||||
| `Pin` | `Ref`, `Source`, `Ahead`, `Behind`, `Pushed` |
|
||||
| `Pinned`, `CheckedOut`, `Tip` | Commits (SHA, subject, author, time) |
|
||||
| `Drift` | Checkout compared with the pin: `Ahead` = commits only the checkout has, `Behind` = commits only the pin has |
|
||||
| `Bases` | `Tip`, `Checkout`, `Committed`: `merge-base <pin> <that commit>` for each commit that is diverged from the pin (ahead and behind); nil otherwise or without a common ancestor |
|
||||
| `TargetTip`, `TargetDrift` | If the pin is not on its target (`off target`): the target's tip and how it compares with the pin, like `Drift` (`Ahead` = commits only the target has); nil/zero otherwise |
|
||||
| `Bases` | `Tip`, `Checkout`, `Committed`, `Target`: `merge-base <pin> <that commit>` for each commit that is diverged from the pin (ahead and behind); nil otherwise or without a common ancestor |
|
||||
| `Committed`, `CommittedDrift` | With a staged pin: the pin in the superproject's HEAD (nil if it is not on disk or the submodule was only added) and how it compares with the staged pin, like `Drift` |
|
||||
| `Changes` | Changed files of the worktree (nil if clean), see below |
|
||||
| `FetchedAt` | Last fetch of the submodule (`FETCH_HEAD` mtime); zero if never |
|
||||
@@ -75,14 +77,19 @@ truth for what counts as a problem.
|
||||
| `missing` | Not initialized; directory missing | Warn |
|
||||
| `off pin` | Checkout differs from pin | Warn |
|
||||
| `changed` | Uncommitted changes; untracked files (worded "untracked repository" if all of them are git repositories) | Warn |
|
||||
| `off target` | Pin is pushed, but not on the target branch (`Pin.Target` is set and differs from `Pin.Ref`, see [Resolving a pin to a ref](#resolving-a-pin-to-a-ref)); the text names the target and the branch the pin is on (`pin not on origin/marco-dev, on origin/main +1`, `+n` for further branches). Not for the superproject | Info |
|
||||
|
||||
Rules:
|
||||
|
||||
- If the submodule is **missing**, that is its only issue (nothing else can
|
||||
be determined).
|
||||
- Issues are returned **most severe first**: unpushed, conflict, off pin,
|
||||
changed.
|
||||
- **Not issues** (quiet): in sync, pin behind/ahead/diverged but pushed,
|
||||
changed, off target.
|
||||
- An unpushed pin is not also `off target`: it has the worse issue.
|
||||
- `off target` does not depend on the superproject's branch: a feature
|
||||
branch of the superproject that pins feature-branch commits shows it too.
|
||||
It is information, not a warning (D26).
|
||||
- **Not issues** (quiet): in sync, pin behind its target (or another ref),
|
||||
staged pin, detached HEAD on the pin. They are shown as information only.
|
||||
A staged pin is also visible in the tree (`staged` or a `●` marker), see
|
||||
[ux-guide.md](ux-guide.md#tree-row), but is never counted as an issue.
|
||||
@@ -94,14 +101,15 @@ Rules:
|
||||
| Level | Meaning | Presentation |
|
||||
|---|---|---|
|
||||
| `LevelQuiet` | Nothing to do | Whole row muted, no word |
|
||||
| `LevelInfo` | Good to know | Blue word |
|
||||
| `LevelWarn` | Look at it | Yellow word |
|
||||
| `LevelDanger` | Act now | Red bold word |
|
||||
|
||||
### Hidden issues
|
||||
|
||||
`Submodule.HiddenIssues()` counts the issues of **all** loaded descendants
|
||||
per level (`Hidden{Warn, Danger}`). A collapsed submodule shows them as `·k`
|
||||
per level, red first, then yellow, so a danger can never hide inside a
|
||||
per level (`Hidden{Danger, Warn, Info}`). A collapsed submodule shows them as `·k`
|
||||
per level, red first, then yellow, then blue, so a danger can never hide inside a
|
||||
collapsed subtree and a warning is never mistaken for one.
|
||||
A descendant whose load failed (`error`) counts as one danger.
|
||||
|
||||
@@ -115,8 +123,9 @@ is never `CheckoutDiffers` (`CheckoutDetached` for a detached HEAD),
|
||||
"HEAD not pushed to any remote" (Danger, like a submodule's pin).
|
||||
|
||||
- **Ref** is the upstream of the current branch (`RefFromCurrentBranch`), so
|
||||
ahead/behind agrees with the header. Closest-branch resolution is only the
|
||||
fallback without an upstream (detached, or no upstream configured).
|
||||
ahead/behind agrees with the header. The target (below) is only the
|
||||
fallback without an upstream (detached, or no upstream configured). The
|
||||
superproject has no `off target` issue.
|
||||
- **Changes** ignore submodules (`status --ignore-submodules=all`): an off-pin
|
||||
or staged submodule is shown by its own row, not twice. A leftover
|
||||
directory of a submodule the branch no longer has is an untracked
|
||||
@@ -125,38 +134,43 @@ is never `CheckoutDiffers` (`CheckoutDetached` for a detached HEAD),
|
||||
|
||||
## Resolving a pin to a ref
|
||||
|
||||
The pin is displayed as a ref, not a hash. A commit can be on several
|
||||
branches, on none, or deep in the history. The git provider shows the
|
||||
**closest** branch and records which rule proposed it in `PinInfo.Source`.
|
||||
Two refs are involved (D26):
|
||||
|
||||
Preferred refs, in this order (each only if it exists):
|
||||
- The **target** is the branch the pin is supposed to be on, the same for
|
||||
everyone: the `branch =` of `.gitmodules` (`.` is the superproject's
|
||||
current branch), else the remote's default branch (`<remote>/HEAD`, else
|
||||
`<remote>/main`, else `<remote>/master`). A declared branch that does not
|
||||
exist locally gives **no** target (the default branch would be a wrong
|
||||
answer). The remote is `origin`, else the first remote. `PinInfo.Target`.
|
||||
- The **ref** is what is displayed, and what `Tip`, `Ahead` and `Behind`
|
||||
refer to. `PinInfo.Ref`, with the rule that found it in `PinInfo.Source`.
|
||||
|
||||
| Preference | Ref | `RefSource` |
|
||||
|---|---|---|
|
||||
| a | `branch = …` in `.gitmodules` | `RefFromGitmodules` |
|
||||
| b | Upstream of the branch checked out in the submodule | `RefFromCurrentBranch` |
|
||||
| c | Remote default branch (`<remote>/HEAD`) | `RefFromDefaultBranch` |
|
||||
|
||||
Resolution:
|
||||
Rules for the ref, in order:
|
||||
|
||||
| # | Rule | `RefSource` |
|
||||
|---|---|---|
|
||||
| 1 | Pin pushed: the branch containing the pin with the fewest commits after it. Candidates are the preferred refs that contain the pin plus any remote branch containing it (`for-each-ref --contains`); a tie goes to the preferred ref | preferred ref's, else `RefFromContains` |
|
||||
| 2 | Pin unpushed: the preferred ref with the fewest commits on either side (`↑n↓m`), ties by preference | preferred ref's |
|
||||
| 3 | A tag (`git describe`) | `RefFromTag` |
|
||||
| 4 | Short SHA | `RefFromSHA` |
|
||||
| 1 | The pin is on the target (a remote branch containing it): the target | `RefFromGitmodules` / `RefFromDefaultBranch` |
|
||||
| 2 | The pin is on other remote branches: the one closest to the pin, fewest commits after it (`rev-list --count <pin>..<branch>`). A tie goes to the upstream of the branch checked out in the submodule, then to the first name in alphabetical order. No branch is a favorite, the default branch included. At most 32 branches are compared (oldest tip first) | `RefFromContains` |
|
||||
| 3 | The pin is on no remote branch (unpushed): the target, for the distance | the target's |
|
||||
| 4 | There is no target: upstream of the branch checked out in the submodule | `RefFromCurrentBranch` |
|
||||
| 5 | A tag (`git describe`) | `RefFromTag` |
|
||||
| 6 | Short SHA; no tip, no distance | `RefFromSHA` |
|
||||
|
||||
So a `.gitmodules` branch is shown when it is as close as any other branch,
|
||||
but a pin that sits on a feature branch shows that branch rather than
|
||||
"diverged from main". The trade-off: a pin on main that a younger branch
|
||||
also contains shows the younger branch if its tip is fewer commits away.
|
||||
Rule 2 is why a pin on a feature branch shows that branch with its real
|
||||
distance (`origin/feat/x ↓1`) instead of "diverged from main". `Ref` differs
|
||||
from `Target` exactly then, and the issue `off target` says so. It does not
|
||||
matter which branch the target is: if `.gitmodules` declares `marco-dev`,
|
||||
`main` is just another branch.
|
||||
|
||||
`Pin.Branches` lists the other remote branches that contain the pin besides
|
||||
`Ref` (oldest tip first, at most 8).
|
||||
|
||||
Distances: `git rev-list --left-right --count <pin>...<ref>` gives
|
||||
`Ahead` (left) and `Behind` (right).
|
||||
`Ahead` (left: commits the pin has that the ref lacks) and `Behind` (right).
|
||||
|
||||
`Pushed` is true if the pin is reachable from any remote ref. A pin that is
|
||||
ahead of its ref can still be pushed (e.g. on another branch); only
|
||||
`Pushed == false` is dangerous.
|
||||
not on its target is `off target` if it is pushed (on another branch), and
|
||||
`unpushed` if it is not.
|
||||
|
||||
## Git commands
|
||||
|
||||
@@ -172,21 +186,17 @@ are local; `<pin>` is the index gitlink.
|
||||
| `Changes` line counts | `diff HEAD --numstat -z -M --ignore-submodules=dirty`, only if a tracked file changed; failure leaves the counts at 0 |
|
||||
| `FileChange.Modified` | `stat` of each changed file that still exists |
|
||||
| `Pushed` | `for-each-ref --contains <pin> refs/remotes` is not empty |
|
||||
| `Pin.Ref` | rules above; the remote is `origin`, else the first remote |
|
||||
| `Pin.Ref`, `Pin.Target`, `Pin.Branches` | rules above; `for-each-ref --contains <pin> refs/remotes` (sorted by commit date), `rev-list --count <pin>..<branch>` per candidate |
|
||||
| `Ahead`, `Behind` | `rev-list --left-right --count <pin>...<ref>` |
|
||||
| `Drift` | `rev-list --left-right --count <head>...<pin>`, only if the checkout differs from the pin |
|
||||
| `Bases` | `merge-base <pin> <ref>` / `<head>` / `<committed>`, only when diverged; then `log -1` of it |
|
||||
| `TargetTip`, `TargetDrift` | `log -1` of the target and `rev-list --left-right --count <target>...<pin>`, only if the ref is not the target |
|
||||
| `Bases` | `merge-base <pin> <ref>` / `<head>` / `<committed>` / `<target>`, only when diverged; then `log -1` of it |
|
||||
| `Committed`, `CommittedDrift` | `ls-tree HEAD` gitlink, if it differs from the pin and exists locally; `rev-list --left-right --count <committed>...<pin>` |
|
||||
|
||||
Details:
|
||||
|
||||
- Preference a: `branch = .` means the superproject's current branch. The
|
||||
ref counts only if `<remote>/<branch>` exists locally.
|
||||
- Preference b uses the checked-out branch's upstream (`<branch>@{upstream}`).
|
||||
- Rule 1 counts `rev-list --count <pin>..<ref>`. Besides the preferred refs
|
||||
it compares at most 16 containing branches (oldest tip first).
|
||||
- Rule 2 counts `rev-list --count <pin>...<ref>`.
|
||||
- Rule 4 shows the short SHA; there is no tip and no distance.
|
||||
- Rule 4 uses the checked-out branch's upstream (`<branch>@{upstream}`).
|
||||
- Rule 6 shows the short SHA; there is no tip and no distance.
|
||||
- `--ignore-submodules=dirty`: changes inside a nested submodule do not make
|
||||
its parent `changed` (D7), but a moved nested pin does.
|
||||
- Renames are detected only for staged moves (`git mv`); an unstaged move
|
||||
@@ -204,7 +214,8 @@ Details:
|
||||
|
||||
`Status.Spine()` arranges the pin, the tip and the checkout as one line of
|
||||
history, newest on top, for the detail pane. Each node is a commit with its
|
||||
roles (`pin`, `tip`, `you`; `HEAD` for the superproject). It uses `Pin.Ahead` /
|
||||
roles (`pin`, `tip`, `you`; `HEAD` for the superproject; `target` for the
|
||||
target branch's tip if the pin is not on it). It uses `Pin.Ahead` /
|
||||
`Pin.Behind` (pin ↔ tip) and `Drift` (checkout ↔ pin).
|
||||
|
||||
- Roles on the same commit share a node (`pin · tip · you`);
|
||||
@@ -214,8 +225,8 @@ roles (`pin`, `tip`, `you`; `HEAD` for the superproject). It uses `Pin.Ahead` /
|
||||
*behind* below it; the `Link` between two nodes counts the commits
|
||||
separating them. The count is the distance, so a tip 4 commits ahead
|
||||
of the pin shows `4 commits`, and an adjacent one `1 commit`.
|
||||
- A commit that has **diverged** from the pin (tip, checkout or committed
|
||||
pin) is drawn as a **fork** if it is the only one and its merge base is
|
||||
- A commit that has **diverged** from the pin (target, tip, checkout or
|
||||
committed pin) is drawn as a **fork** if it is the only one and its merge base is
|
||||
known (`Status.Bases`): it is the first node (`SpineNode.Fork`), with the
|
||||
number of commits down to the base as its `Below`; the main lane follows
|
||||
(pin and the linear nodes), and a `RoleBase` node where the two histories
|
||||
|
||||
+25
-6
@@ -82,7 +82,7 @@ For the superproject (header selected), the `pin` and `you` roles become
|
||||
1. Directory (muted) and name (bold); `fetched <age>` of the submodule,
|
||||
muted, right-aligned in the name's line (left out if the pane is too
|
||||
narrow, or the submodule is missing)
|
||||
2. One line per issue: word (colored, 10 columns) + explanation;
|
||||
2. One line per issue: word (colored, 11 columns) + explanation;
|
||||
`in sync nothing to do` if there are none and no pin is staged;
|
||||
`staged` and `detached HEAD on pin` as information
|
||||
3. `Changes` (only with uncommitted changes), see
|
||||
@@ -107,7 +107,8 @@ you ● 48005ac Merge branch 'feat/ethercat…
|
||||
position, not by comparing SHAs. The commits between two nodes are not
|
||||
listed, only counted (`┊ 4 commits`; `1 commit` if adjacent).
|
||||
- The label column holds the roles (`pin`, `tip`, `you`; `HEAD` for the
|
||||
superproject), joined by ` · ` if they sit on one commit
|
||||
superproject; the target's tip is labelled with the name of its branch, e.g.
|
||||
`marco-dev`, without the remote and cut at 16 columns; `target` if unknown), joined by ` · ` if they sit on one commit
|
||||
(`pin · tip`, `pin · you`). If all of them sit on one commit it says
|
||||
`in sync` instead, which also keeps the commit column in line with the
|
||||
other values; the column only grows for a longer label.
|
||||
@@ -116,8 +117,25 @@ you ● 48005ac Merge branch 'feat/ethercat…
|
||||
visible as a distance between two nodes. The committed pin is left out if
|
||||
it is not on disk. If the staged pin is *older* than the committed one it
|
||||
sits below it, and the gap above it says `(staged pin moves back)` (blue).
|
||||
- The checkout (`you`) is yellow (label and SHA) when it is on its own node,
|
||||
i.e. off pin. Everything else is the default text color, the gap muted.
|
||||
- If the pin is `off target`, the target branch's tip is on the spine,
|
||||
labelled with the name of its branch (`marco-dev`, without the remote, cut
|
||||
at 16 columns), so the distance from main is visible: below the pin if the pin is
|
||||
on top of the target, a fork if both have commits of their own. `tip` is
|
||||
then the tip of the branch the pin is on (the `Ref`):
|
||||
|
||||
```
|
||||
marco-dev ● d0bbbd7 updated submodules
|
||||
┊ 12 commits
|
||||
tip ● ┊ a523224 Remove stale entry
|
||||
┊ ┊ 1 commit
|
||||
pin · you ● ┊ 5a7df75 Merge branch 'ethercat…
|
||||
┊ ┊ 52 commits
|
||||
base ●─╯ 6707725 updated submodule
|
||||
```
|
||||
- The role words are muted, each word on its own: `you` is bold in the
|
||||
default text color, so the checkout stands out in `pin · you`. On its own
|
||||
node, i.e. off pin, it is yellow (word and SHA); `staged` is blue. Commit
|
||||
subjects use the default text color, the gap is muted.
|
||||
- A commit that has **diverged** from the pin gets its own lane to the right
|
||||
of the main one. The two lanes join at a `base` node, the commit where the
|
||||
histories split; the counts say how many commits each side has since:
|
||||
@@ -198,7 +216,7 @@ branch and state stay at the left. If the line is too narrow it is cut with
|
||||
`…` at the right end, so the most important counts stay.
|
||||
|
||||
Issue counts are ordered by severity (unpushed, conflict, missing, off pin,
|
||||
changed), each in its level color. Zero counts are omitted. `n loading`
|
||||
changed, off target), each in its level color. Zero counts are omitted. `n loading`
|
||||
counts only submodules whose status is still being loaded; ones whose load
|
||||
failed are counted separately as `n error` (red, before the issue counts). A detached
|
||||
superproject shows `(detached)` as its branch.
|
||||
@@ -224,7 +242,7 @@ colors in components.
|
||||
|---|---|---|
|
||||
| Danger | ANSI `1` red, bold | `unpushed`, `conflict`, `error`, `↑n` of an unpushed pin |
|
||||
| Warn | ANSI `3` yellow | `missing`, `off pin`, `changed`, differing checkout SHA |
|
||||
| Info | ANSI `4` blue | `staged`, the `●` staged marker |
|
||||
| Info | ANSI `4` blue | `staged`, the `●` staged marker, `off target` |
|
||||
| Primary | ANSI `6` cyan | branch names, commit hashes, spinner |
|
||||
| Muted | ANSI `8` grey | quiet rows, directory headers, arrows, labels |
|
||||
| Text | terminal default | normal text |
|
||||
@@ -248,6 +266,7 @@ colors in components.
|
||||
| `missing` | not initialized / directory missing |
|
||||
| `off pin` | checkout differs from pin |
|
||||
| `changed` | uncommitted changes / untracked files |
|
||||
| `off target` | pin not on `<target>`, on `<branch>` (+n more) |
|
||||
| `staged` | pin change staged, not committed |
|
||||
| `in sync` | nothing to do |
|
||||
|
||||
|
||||
Reference in New Issue
Block a user