Skip to content

fix(digest): explicit force-with-lease in rebaser push - #9

Merged
dnplkndll merged 1 commit into
mainfrom
fix/rebaser-explicit-lease
Jun 15, 2026
Merged

fix(digest): explicit force-with-lease in rebaser push#9
dnplkndll merged 1 commit into
mainfrom
fix/rebaser-explicit-lease

Conversation

@dnplkndll

Copy link
Copy Markdown
Contributor

Run #2 of the digest rebased all 16 ddmrp MIG branches + 3 fixes cleanly, but every push was rejected with ! [rejected] (stale info) — a bare --force-with-lease false-positive against a tracking ref populated by an explicit-refspec fetch (not auth, not the PAT). Pin the lease to the exact sha we fetched (refs/heads/<b>:<oid>): same race protection, no false stale. Regression test pins the explicit-lease push form. (3 19.0-fix-* branches separately conflict in test_ddmrp.py — manual triage, likely already-superseded fix branches.)

Bare --force-with-lease reports '! [rejected] (stale info)' against a
tracking ref that was set via an explicit-refspec fetch, so all 19
clean ddmrp rebases failed to push. Pin the lease to the sha we just
fetched (refs/heads/<b>:<oid>) — keeps the race guard, drops the false
stale. Test asserts the explicit-lease push form.
@dnplkndll
dnplkndll merged commit 586dd11 into main Jun 15, 2026
1 check passed
@dnplkndll
dnplkndll deleted the fix/rebaser-explicit-lease branch June 15, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant