Skip to content

chore(workflows): rename local job to pr-check so check prefix matches branch protection - #61

Merged
ciotlosm merged 1 commit into
mainfrom
chore/rename-local-job-to-pr-check
Jul 11, 2026
Merged

ciotlosm merged 1 commit into
mainfrom
chore/rename-local-job-to-pr-check

Conversation

@ciotlosm

Copy link
Copy Markdown
Member

Summary

Branch protection now requires the new pr-check / ASCII-only check and pr-check / Standards drift check contexts. The local job was still named shared, producing checks prefixed with shared: instead. Without this rename, the PR can never satisfy the required status checks.

Also bypasses the pr-check.yml wrapper and calls pr-validation.yml@v23 directly. The wrapper adds an extra job layer that makes the check name harder to read.

Refs: n3ary/actions#35, n3ary/actions#36

…s branch protection

Branch protection now requires "pr-check / ASCII-only check" and
"pr-check / Standards drift check" (set up to match the new
shared wrapper contract). The local job was still named "shared",
producing checks prefixed with "shared:" instead. Without this
rename, the PR can never satisfy the required status checks.

Also bypasses the pr-check.yml wrapper and calls
pr-validation.yml@v23 directly. The wrapper adds an extra job
layer ("pr-check:pr-validation:ascii-check") that made the check
name harder to read. With the direct call + the local job
renamed to "pr-check", the check name is the clean
"pr-check:ascii-check" / "pr-check:Standards drift check" the
branch protection expects.

Refs: n3ary/actions#35, n3ary/actions#36
@ciotlosm
ciotlosm merged commit 090dd83 into main Jul 11, 2026
3 checks passed
@ciotlosm
ciotlosm deleted the chore/rename-local-job-to-pr-check branch July 11, 2026 13:40
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