Repository navigation
Follow-ups after the switch to fast-forward pushes #294
Description
Pull requests land by a fast-forward push since 2026-11-13 (#293; rulesets "main (no bypass)" and "main: pull request (admin push bypass)"). Left over:
-
.github/: comments and messages still describe squash merges (release.ymlheader and lookup comments,release-guard.shmessages,ci.ymlheader,codeql.yml, the(#NN)checkbox inPULL_REQUEST_TEMPLATE.md). Wording only, no functional change; waits until no pre-release is in acceptance. -
nova-merge-train.js, cleanup mode: reportspartialwhen GitHub already deleted the pull request's branch after the push. That is the expected case and should not count as a problem. - First release under the new flow: run the "Release dry run" from
HANDOFF.mdafter pushingmainand before pushing the tag. The lookup of the CI run by the tagged commit itself has not run in production yet. - Renovate pull requests: confirm on the first one that its rebase trigger works and that the pin check in the merge train covers it.
Proven on 2026-11-13: a push of an unchecked commit to main is refused (GH013, required status check build); a push of a pull request's green head commit is accepted, the pull request is marked merged and its branch is deleted.
🤖 Generated with Claude Code
Activity
nofuturekid commentedon Nov 13, 2026
Pull request #313 covers:
nova-merge-train.jscleanup: a remote branch already deleted by GitHub is no longer a problem (second item).nova-pr.js: the pull request is established from the branch by the script, not from the builder'spr_number.nova-pr.js: optional task fieldclosesfor umbrella issues (Refs #<n>, no closing keyword)./tmpnote in both headers.The other items stay open.
🤖 Generated with Claude Code