Repository navigation
feat(series): Mint main-dev's extension without pushing it, with --no-push-dev - #2961
Merged
krlmlr merged 1 commit intoOct 18, 2026
Conversation
…-no-push-dev` Stage 5 pushes `-dev` as soon as it has minted the extension, and the push starts an each-rcc run whenever the branch's concurrency group is idle. When R-side fixes or a doc sweep wait to be folded into the new commits, that run judges commits known to be broken and has to be cancelled. `scripts/series-advance.sh --no-push-dev` mints the extension exactly as before and writes it to the local ref `refs/series/<S>-dev-next` instead of pushing it. Green, its mirror and `-build-base` move as always. The stage prints the `git push --force-with-lease` that publishes the folded tip, leased on the `-dev` the run read. A replay stopped under the option records it in the state file, so `--continue` keeps it even when it is left off, and `--abort` drops an unpushed `-dev-next` as well as a stopped replay. The default is unchanged. `scripts/series-advance-test.sh` gains claim 22, and `scripts/series-args-test.sh` checks the flag; the series-loop skill says when to use it, in stage 5 and `references/5-extend.md`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JXnA76zWTu4ZD8BQCSYRpk
This was referenced Oct 17, 2026
Merged
1 task
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #2959 (base
claude/series-window-and-harness), which also touchesscripts/series-advance.sh; this diff shows only the new option.Why
Stage 5 of the series loop pushes
-devas soon asscripts/series-advance.shhas minted the extension. That push starts aneach-rccrun whenever the branch's concurrency group is idle (each.yamlruns on pushes to*-dev, groupeach-rcc-<ref>, no cancel-in-progress). The operator usually has R-side fixes or a doc sweep ready to fold into the newly extended commits, so CI starts on commits known to be broken, and the run has to be cancelled by hand. The rule "push-devonce there are at least five validated commits" only holds without exceptions if the extension can be minted locally and pushed by the operator.What
scripts/series-advance.sh <S> --no-push-devruns stage 3 exactly as before: green fast-forwards, is mirrored, and-build-baseis set. Stage 5 mints the extension exactly as now, on both the plain ref move and the replay. It then writes the new tip to the local refrefs/series/<S>-dev-next(with a reflog, so a rerun that replaces it loses nothing) instead of pushing-dev.-devthe run read. The operator first runsgit update-refto point the ref at the folded tip (or names that tip in its place):git push --force-with-lease=refs/heads/<S>-dev:<sha> <remote> refs/series/<S>-dev-next:refs/heads/<S>-devIts first line reads
dev not pushed: …rather thandev -> …, so nobody takes it for a moved-dev.--continue: a replay stopped under the option records it as a fifth field of the state file, so a--continuethat leaves the option off still pushes nothing. Old four-field state files read as before.--abortalso drops an unpushedrefs/series/<S>-dev-next, alongside a stopped replay. It still writes no remote ref.--no-check-glue.SKILL.mdstage 5 and a paragraph under "After the push" inreferences/5-extend.md. The details stay in the script header. The handbook leaf is unchanged, since it leaves how to run a firing to the playbook.Verification
scripts/series-advance-test.sh: 147 passed, 0 failed (124 before). Claim 22 adds two offline fixtures:hold, the plain ref move with a green to advance: green, its canonical copy and-build-basemove,-devis not written, and the local ref holds the extension. The printed push is checked verbatim, then run, and it publishes the extension.stay, a replay that conflicts: the stop records the option, a--continuewithout it finishes the chunk locally with the counter restamped, and--abortthen drops the ref while-devstays put.scripts/series-args-test.sh: 87 passed (85 before):--no-push-devis not a usage error, and--helplists it.scripts/series-port-test.sh: 17 passed.scripts/series-advance.shandscripts/series-args-test.share clean.scripts/series-advance-test.shhas the same findings as the base branch, none in the new lines..claude/skills/docs-consistency/scripts/check-handbook.sh: clean (49 pages, 68 secondary documents).LLM use: this PR was prepared with Claude Code (Claude Opus 5.5), at the maintainer's request.
🤖 Generated with Claude Code
https://claude.ai/code/session_01JXnA76zWTu4ZD8BQCSYRpk
Generated by Claude Code