Skip to content

DO NOT MERGE: validate release-artifacts status check names - #464

Closed
tinder-maxwellelliott wants to merge 2 commits into
masterfrom
maxwelle/ci-check-validation
Closed

DO NOT MERGE: validate release-artifacts status check names#464
tinder-maxwellelliott wants to merge 2 commits into
masterfrom
maxwelle/ci-check-validation

Conversation

@tinder-maxwellelliott

Copy link
Copy Markdown
Collaborator

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 deploy job to release-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

  • Exactly three release-artifacts (<os>) checks appear and pass
  • No check named deploy (…) appears
  • The PR reports mergeable rather than blocked

Close without merging once green, and delete docs/ci-check-validation-scratch.md along with the branch.

🤖 Generated with Claude Code

tinder-maxwellelliott and others added 2 commits August 16, 2026 13:07
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>
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.

1 participant