ci(cutover): the wipe-day cutover's trigger on main (D332) #26
Reference in New Issue
Block a user
No description provided.
Delete Branch "ci/cutover-trigger"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What & why
The wipe-day cutover's trigger, onto
mainonce (D332, "First run"). Gitea fires a schedule only from the default branch.This PR holds one file:
.gitea/workflows/cutover.yml, byte-identical to the copy onedge(blob4ec300c). It is the trigger and the step wiring only; every step checks outedgeand runsedge's scripts. So nothing else ofedgecomes with it, and the November field list stays onedgeuntil the cutover itself merges it.It is a
ci:commit, sorelease.ymlcuts no release.Merge order: merge the feature PR into
edgefirst, so Thursday's first run findstools/drill/cutover.jsthere. After that, no wipe needs an approval.How it was tested
The file is the one tested on the feature branch: 85 tests pass, and a dry run (CI run 54) went through every gate. See the
edgePR.Checklist
AI-assisted contributions (required)
Claude Code (Claude Opus 5.5). I have reviewed and understandevery change, and take responsibility for it. AI-authored commits are
marked with a
Co-Authored-By/Assisted-Bytrailer.License
(GNU GPL v3.0 or later), and I have the right to contribute it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY