Skip to content

Turn on deleting merged branches, and read it in Verify - #6

Merged
ftymoshchuk merged 1 commit into
mainfrom
claude/amazing-bohr-ftes98
Nov 18, 2026
Merged

ftymoshchuk merged 1 commit into
mainfrom
claude/amazing-bohr-ftes98

Conversation

@ftymoshchuk

Copy link
Copy Markdown
Member

What this changes

docs/new-repository.md left out the one repository setting beside the ruleset: 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" now turns it on, and Verify reads it back.

Setting those two up turned up three more things the page now says:

  • The reviewed ruleset file can be read from GitHub without a clone, which is how pageant and tollhouse got theirs; 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, as herald's is: another name, an always bypass, no up-to-date rule, and a merge_queue rule. It is replaced in place with the reviewed file.

Does a caller see it?

  • No: docs, CI or tests only. Neither action changes.

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} reads true for tollhouse and herald, and the ruleset line prints default-branch / branch / active / ["pull_request"] for tollhouse, and main / branch / active / ["always"] and release tags / tag / active / ["always"] for herald. The no-clone POST and the PATCH are the commands that set pageant and tollhouse up on 2026-11-18.

Checks

  • Every uses: inside an action names a 40-character commit with its # vX.Y.Z (no action changes)
  • A caller's input reaches a shell through env:, never written into run: (no action changes)
  • CHANGELOG.md has a line under Unreleased

Generated by Claude Code

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
@ftymoshchuk
ftymoshchuk merged commit a2dc8ed into main Nov 18, 2026
7 checks passed
@ftymoshchuk
ftymoshchuk deleted the claude/amazing-bohr-ftes98 branch November 18, 2026 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants