chore(workflows): delete obsolete promote/sync workflows (Phase 3C of internal#81) #119
cp-lead
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "chore/trunk-based-delete-obsolete-workflows"
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?
Summary
Final cleanup for the trunk-based migration on
molecule-core. Deletes 6 workflows that all existed to manage the staging↔main branch dance — a dance that trunk-based makes obsolete:auto-promote-staging.yml— fast-forward staging→main on greenauto-promote-on-e2e.yml— alt promote path on E2E greenauto-promote-stale-alarm.yml— alarm if staging promotion stallsauto-sync-main-to-staging.yml— sync main→staging after UI mergesauto-sync-canary.yml— dry-run probe of the auto-sync token+push pathretarget-main-to-staging.yml— rebase open PRs onto stagingAfter Phase 3A (#108 promoted 5 staging-only feature PRs to main, just merged) and Phase 3B (#109 dropped staging-branch triggers from the 4 e2e workflows), main is the only branch CI cares about. None of the above workflows have anything to do; they're 1977 lines of dead
Go-time-no-Gitea-time-yescode.Rollback
git revertthis commit to restore the workflows. They still work mechanically; trunk-based just doesn't need them.Follow-up
The
stagingbranch on the remote is deleted in a follow-up step (git push origin --delete staging) after this PR merges, so reviewers can confirm CI runs cleanly on the new shape before the ref disappears.Closes internal#81 trunk-based migration tracking issue (Phase 3 final step).
🤖 Generated with Claude Code
Trunk-based migration final cleanup for molecule-core. The 6 workflows deleted here all existed to manage the staging↔main branch dance that trunk-based makes obsolete: - auto-promote-staging.yml fast-forward staging→main on green - auto-promote-on-e2e.yml alt promote path on E2E green - auto-promote-stale-alarm.yml alarm if staging promotion stalls - auto-sync-main-to-staging.yml sync main→staging after UI merges - auto-sync-canary.yml dry-run probe of the auto-sync token+push path - retarget-main-to-staging.yml rebase open PRs onto staging After Phase 3A (PR #108 promoted 5 staging-only feature PRs to main) and Phase 3B (PR #109 dropped staging-branch triggers from the 4 e2e workflows), main is the only branch the CI cares about. None of the above workflows have anything to do; they're 1977 lines of dead Go-time- no-Gitea-time-yes code. Rollback: `git revert` this commit to restore the workflows. They still work mechanically; trunk-based just doesn't need them. The `staging` branch on the remote is deleted in a follow-up step (`git push origin --delete staging`) after this PR merges, so reviewers can confirm CI runs cleanly on the new shape before the ref disappears. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>LGTM. Phase 3C of internal#81 — final cleanup of the trunk-based migration on molecule-core. Deletes 6 promote/sync workflows that were orchestrating the staging↔main dance. Reviewed: every deletion is a workflow whose entire purpose was branch coordination, all replaced by trunk-based shape. Required check Secret scan green; Platform (Go) green.
LGTM. Phase 3C of internal#81 — final cleanup of the trunk-based migration on molecule-core. Deletes 6 promote/sync workflows that were orchestrating the staging↔main dance. Reviewed: every deletion is a workflow whose entire purpose was branch coordination, all replaced by trunk-based shape. Required check Secret scan green; Platform (Go) green.