family.py bump --to: pins a commit only the member's mount holds, which bump-leg.py refuses as local-only

bump --to should refuse a commit that no branch of the member's remote reaches, as bump-leg.py does.

From the checklist triage of 2026-10-15; Brett Heap approved its recommendations at 2026-10-15T16:49:38Z. One pull request covers the lines below.

Decision applied: the triage's D2, option 1: refuse it as bump-leg.py does (member-to-local-only), answering from the remote-tracking refs when offline. About 12 tests bump to such a commit and would push it first.

Lines

568/1: bump --to pins a commit only the member's mount holds; bump-leg.py refuses that case as local-only. Where: scripts/family.py _checked_to_names_a_commit (:4099, cat-file -t only); scripts/bump-leg.py :971-985. Effort M; all. On main 26c1600: Probe p01 at 26c1600: bump exits 0, HEAD's gitlink is the mount-only commit, validate-family.py exits 0 and the member's remote lacks the object; main's own test_bump_dry_run_leaves_a_linked_manifest_to_the_real_run pins such a commit; family.py: bump --to asks add's duplicate-id question, peels an annotated tag's own id as add --at does, and says to push first a commit the member does not hold after its fetch (#541) #568 (8890f57) left this as a checklist line. (source)

Each line above is marked → this issue on its tracking issue. Tick it there too when this closes.

The lines as written on the tracking issues

bump --to pins a commit that only the member's mount holds, where bump-leg.py refuses it as bump-leg-commit-local-only.

A commit made inside members/<P> and never pushed passes bump's object check, because the object is in the mount's store. It is pinned with exit 0, and the holder then cannot be bootstrapped anywhere else.

Refusing it needs a ruling on offline bumps: today a bump whose fetch failed goes on from the objects the member already has.

Under bump-leg.py's reachability rule, at least 12 test cases in 5 files fail, and 6 of them build their target with commit_in_mount.

— #459, comment

CLAIMED — lane openRepoShape-4, session 11c6c0ef-495a-4a05-94cf-811b7b0a1012@Eagle, 2026-10-15T20:36:00Z, for #613

Logged in lanes/log/openRepoShape-4.md at 5db78258156c55c79299d7b6b5df36ec30a00477.

The three reads (lane-collision-protocol Rule 1):

1. existing `CLAIMED —` comments on opensoft/openRepoShape#613:
   none
2. `gh pr list --repo opensoft/openRepoShape --state all --search "#613"`, kept where the row or its body names `#613`:
   none
3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `613` as a whole token:
   none

family.py: #625 fix round 1: a test that a commit only another remote…

Merge main (8f453d0) into fix/family-verbs-refuse-up-front

family.py: `bump` fetches every branch of the member's `origin` whate…

shape_materialize.py and bump-leg.py: the fetch for a branch's answer…

Navigation Menu

Repository navigation

family.py `bump --to`: pins a commit only the member's mount holds, which `bump-leg.py` refuses as local-only #613

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

family.py bump --to: pins a commit only the member's mount holds, which bump-leg.py refuses as local-only #613

Description

Activity

brettheap commented on Oct 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

family.py `bump --to`: pins a commit only the member's mount holds, which `bump-leg.py` refuses as local-only #613