Finding
Three branches on this repo carry unlanded commits and no PR was ever opened for any of them.
They are invisible to every check someone would normally run: they do not appear in a PR list, they
are not stale-marked, and git branch shows them looking like any other branch.
One of the three turned out to contain a live correctness fix for a capability this repo had since
advertised to an adopting repo.
Evidence
Compared against main via the API (a --depth 1 clone reports these as empty, which reads as
"nothing to recover" — worth knowing before anyone re-derives this):
| branch |
ahead |
files |
what it does |
fix/hybrid-gate-docs-only-diff-range |
1 |
1 |
Recovered — see #40. Diffs the docs-only changeset from the merge-base rather than the base tip. |
fix/235-push-event-requires-build |
1 |
3 |
Makes a push to the default branch require a real build, so a break that lands on main is not discovered by the next PR to inherit it. Adds scripts/check_gate_evaluation.py (+94). |
fix/gate-push-event-trailer-sha |
6 |
4 |
Survives a push event in the trailer-verify step; stops failing the build when FLEET_REPO_TOKEN is absent; adds scripts/check_event_shape_guards.py (+228). |
fix/235-push-event-requires-build's own commit message states the gap precisely: "On a push the
verdict ladder never reached the build result" — adding push: to a caller is the trigger half, and
this is the half that makes the trigger mean something. It references theatron#235.
Why this matters
These are reusable workflows, so a correctness gap here is inherited by every adopting repo rather
than confined to one. That is exactly what happened with the docs-only branch: the two-dot diff bug
sat unlanded while docs_only was exposed as a workflow_call output in #35 and recommended to an
adopting repo as the way to skip expensive jobs. The verdict silently flips to false whenever the
base moves — which on an active repo is immediately.
The other two are the same shape: correctness work on the shared gate that is finished, unreviewed,
and reachable only by someone who thinks to enumerate branches.
The class is worth naming beyond these three. A branch with no PR is not merely untracked — it is
unreviewable, because nothing invites review. The work was done and then made invisible by
omission rather than decision.
Desired correction
For each remaining branch, one of: open it as a PR and land it, or close it with a stated reason and
delete the branch. Not left as-is — that is the state that produced this issue.
Sequencing note for whoever picks these up: fix/gate-push-event-trailer-sha is 6 commits and 11
behind main, and one of its commits (fix(hybrid-gate): stop failing the build when FLEET_REPO_TOKEN is absent) may already be superseded by the dependabot-credential fix that landed
separately. Verify what is still needed against current main before rebasing the whole thing —
test whether the capability is present, not whether the lines are.
Done when: no branch on this repo has unlanded commits without either an open PR or a recorded
decision to drop it.
Finding
Three branches on this repo carry unlanded commits and no PR was ever opened for any of them.
They are invisible to every check someone would normally run: they do not appear in a PR list, they
are not stale-marked, and
git branchshows them looking like any other branch.One of the three turned out to contain a live correctness fix for a capability this repo had since
advertised to an adopting repo.
Evidence
Compared against
mainvia the API (a--depth 1clone reports these as empty, which reads as"nothing to recover" — worth knowing before anyone re-derives this):
fix/hybrid-gate-docs-only-diff-rangefix/235-push-event-requires-buildmainis not discovered by the next PR to inherit it. Addsscripts/check_gate_evaluation.py(+94).fix/gate-push-event-trailer-shaFLEET_REPO_TOKENis absent; addsscripts/check_event_shape_guards.py(+228).fix/235-push-event-requires-build's own commit message states the gap precisely: "On a push theverdict ladder never reached the build result" — adding
push:to a caller is the trigger half, andthis is the half that makes the trigger mean something. It references theatron#235.
Why this matters
These are reusable workflows, so a correctness gap here is inherited by every adopting repo rather
than confined to one. That is exactly what happened with the docs-only branch: the two-dot diff bug
sat unlanded while
docs_onlywas exposed as aworkflow_calloutput in #35 and recommended to anadopting repo as the way to skip expensive jobs. The verdict silently flips to
falsewhenever thebase moves — which on an active repo is immediately.
The other two are the same shape: correctness work on the shared gate that is finished, unreviewed,
and reachable only by someone who thinks to enumerate branches.
The class is worth naming beyond these three. A branch with no PR is not merely untracked — it is
unreviewable, because nothing invites review. The work was done and then made invisible by
omission rather than decision.
Desired correction
For each remaining branch, one of: open it as a PR and land it, or close it with a stated reason and
delete the branch. Not left as-is — that is the state that produced this issue.
Sequencing note for whoever picks these up:
fix/gate-push-event-trailer-shais 6 commits and 11behind
main, and one of its commits (fix(hybrid-gate): stop failing the build when FLEET_REPO_TOKEN is absent) may already be superseded by the dependabot-credential fix that landedseparately. Verify what is still needed against current
mainbefore rebasing the whole thing —test whether the capability is present, not whether the lines are.
Done when:no branch on this repo has unlanded commits without either an open PR or a recordeddecision to drop it.