Repository navigation
Store Required Checks within the repo - #1401
Merged
Merged
Conversation
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.
Currently, "required checks" on PRs are hidden from maintainers, and can get out of sync with the reality of a repo. To fix this, we're adding a
.github/required-checks.ymlfile, which lists the checks that must pass before a PR can merge into main.When this file is changed, the ruleset that manages branch protection automatically gets synced up. The new
Required checksworkflow checks that all the checks listed inrequired-checks.ymlexist.(Sidenote: I'm increasingly wary of agents that have access to GitHub mistakenly (or potentially nefariously) doing things that could do us damage or cause us to have unexpected or high costs. That's why I'm using CODEOWNERS on a more frequent basis for files that are always worth just getting a second pair of eyes on. It's not a reflection on trust for maintainers 🙂)
The file adds the following Required Checks:
configlet / configleti18n / completenesschecktestValidate required checks(rather recursively, I admit!)🤖 Generated with Claude Code