From bae564f18c1e399e0e98f7f66bf666a654518717 Mon Sep 17 00:00:00 2001 From: Kyle Sexton <153232337+kyle-sexton@users.noreply.github.com> Date: Fri, 13 Nov 2026 20:14:16 -0500 Subject: [PATCH] docs: name the required check CI Status CONTRIBUTING.md and the pull request template still named the required check `ci-status`. The org ruleset requires `CI Status`. Co-Authored-By: Claude Fable 5.2 --- .github/PULL_REQUEST_TEMPLATE.md | 2 +- CONTRIBUTING.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index d11587b..018af34 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -14,7 +14,7 @@ No related issue: The reason is required. Write the escape without backticks: the gate masks inline code spans before matching, so a backticked escape is invisible to it and the PR draws the advisory `needs-issue-linkage` label anyway. The linkage -rule is advisory: the `check-contract` step inside `ci-status` leaves a comment and +rule is advisory: the `check-contract` step inside `CI Status` leaves a comment and the `needs-issue-linkage` label instead of failing. That step's output reports the exact rule it applied and is authoritative over this comment. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 42c41bf..5cfd8e8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -15,7 +15,7 @@ A repository's own `CONTRIBUTING.md`, with project-specific details, overrides t 3. Ensure the project builds and its checks pass locally. 4. Open a pull request, fill out the template, and link the related issue. - Title it in [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) form with a standard type, `[optional scope]: `, for example `feat(api): add pagination`. The title becomes the squash-merge commit subject on the default branch. - - Where the repository enforces this, the `ci-status` check reports on your pull request and must pass before merge. + - Where the repository enforces this, the `CI Status` check reports on your pull request and must pass before merge. 5. Address review feedback. Pull requests are squash-merged once every review thread is resolved and any required checks pass. ## Reporting security issues