Repository navigation
Turn on deleting merged branches, and read it in Verify - #6
Merged
Merged
Conversation
The page named the branch ruleset as the one setting no pull request reviews, and left out the repository setting beside it: deleting a branch once its pull request merges. A new repository starts with it off, so pageant and tollhouse went without it while every other public repository had it on. - "Apply it to a new repository" turns it on, and Verify reads it back with a row of its own in the healthy table. - The reviewed ruleset file can be read from GitHub without a clone, which is how pageant and tollhouse got theirs on 2026-11-18; the "no such file" row points at it. - Verify prints each ruleset's target, so a tag ruleset (herald's "release tags") is not read as a second ruleset stacked on the branch. - A row for a branch ruleset made by hand: another name, an `always` bypass, no up-to-date rule or an extra rule such as `merge_queue`, as herald's has; it is replaced in place with the reviewed file. Each new filter was run over what the API returns for tollhouse and herald. Documentation only; neither action changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UrD7sKbooiWZ4SqzxVSvGN
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.
What this changes
docs/new-repository.mdleft out the one repository setting beside the ruleset: deleting a branch once its pull request merges. A new repository starts with it off, sopageantandtollhousewent without it while every other public repository had it on. "Apply it to a new repository" now turns it on, and Verify reads it back.Setting those two up turned up three more things the page now says:
pageantandtollhousegot theirs; the "no such file" row points at it.herald'srelease tags) is not read as a second ruleset stacked on the branch.herald's is: another name, analwaysbypass, no up-to-date rule, and amerge_queuerule. It is replaced in place with the reviewed file.Does a caller see it?
The CI step that fails without it
None; this is documentation only. Each new filter was run over what the API returns:
{delete_branch_on_merge}readstruefortollhouseandherald, and the ruleset line printsdefault-branch / branch / active / ["pull_request"]fortollhouse, andmain / branch / active / ["always"]andrelease tags / tag / active / ["always"]forherald. The no-clonePOSTand thePATCHare the commands that setpageantandtollhouseup on 2026-11-18.Checks
uses:inside an action names a 40-character commit with its# vX.Y.Z(no action changes)env:, never written intorun:(no action changes)CHANGELOG.mdhas a line under UnreleasedGenerated by Claude Code