Repository navigation
docs: main has a ruleset, and three places said it did not - #144
Merged
Merged
Conversation
The ruleset of #74 was created on 2026-10-12: a pull request, green `check` and `secrets`, no force push, no deletion, no bypass. Requiring a branch to be up to date was left off for its cost in Actions runs. CLAUDE.md says what the ruleset does, that a renamed CI job blocks every merge until the ruleset is changed with it, and what it still does not cover. ADR-012's context and decision 3 are corrected in place with dated blocks, per the index's own rule; decisions 1 and 2 are unchanged. Docs only: no bump, bin/bouncer.cjs unchanged. Closes #74 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
maingot a ruleset on 2026-10-12 (rules/24943470), which made three statements merged earlier the same day false. This corrects them.check,secrets(GitHub Actions)ci.ymlblocks every merge until the ruleset is changed with it, and that two green PRs can still leavemainred.Cost
Docs only. No bump, bundle unchanged. From here every merge needs a green run of both jobs, about 45 s of Actions time, which every PR was already spending.
This PR is also the first one merged under the ruleset.
Closes #74
🤖 Generated with Claude Code