DO NOT MERGE: validate release-artifacts status check names - #464
Closed
tinder-maxwellelliott wants to merge 2 commits into
Closed
DO NOT MERGE: validate release-artifacts status check names#464tinder-maxwellelliott wants to merge 2 commits into
tinder-maxwellelliott wants to merge 2 commits into
Conversation
Throwaway PR to confirm that the checks CI emits on a master-based branch match the contexts branch protection now requires, after #463 renamed deploy -> release-artifacts. Co-Authored-By: Claude Opus 5 (1M context) <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.
Purpose
Throwaway draft PR. It exists only to confirm that the status checks CI emits on a master-based branch match the contexts branch protection requires, after #463 renamed the
deployjob torelease-artifacts.Branch protection was updated to require:
release-artifacts (ubuntu-latest)release-artifacts (macos-latest)release-artifacts (windows-latest)replacing four stale
deploy (…)contexts — one of which was a truncated UI label (--legacy_...) that could never have matched a real check name.Pass criteria
release-artifacts (<os>)checks appear and passdeploy (…)appearsClose without merging once green, and delete
docs/ci-check-validation-scratch.mdalong with the branch.🤖 Generated with Claude Code