Repository navigation
ci: remove only demonstrably ancestor-only obsolete branches - #340
Merged
Merged
Conversation
2 of 7 tasks
github-actions
Bot
deleted the
ci/prune-proven-ancestor-branches-20261028
branch
October 28, 2026 12:11
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.
Scope
Extend successful merged-head cleanup #336 to remove a second, rigorously provable category: a nonreserved, nonprotected, nondefault, non-open-PR topic branch with zero unique commits ahead of main (GitHub compare status behind/identical). Guard all previously preserved release/deployment/history names.
Evidence: after cleanup, remote only has
main,fix/release-keyword-compat, andpr-259. Verifiedpr-259hasahead_by=0,behind_by=123; it is fully contained in main. Verifiedfix/release-keyword-compathas one unique ahead commit, so must remain untouched.The script re-reads branch SHA/protection, open PRs and default-branch ancestry immediately before deleting. PR heads exactly matching an actually merged PR retain prior protection. No other repositories, runtime APIs, license, release assets or user data touched. GitHub compare/delete cannot be atomic; documented residual race remains. Requires full current-head Rivet CI before merge, then verify GitHub cleanup run and remote refs. Tracks portfolio branch hygiene #10.