Skip to content

ci: keep PR text out of the required dash check, and let PR title runs finish - #23

Merged
NSchatz merged 1 commit into
mainfrom
ci/dash-split-pr-title
Nov 8, 2026
Merged

NSchatz merged 1 commit into
mainfrom
ci/dash-split-pr-title

Conversation

@NSchatz

@NSchatz NSchatz commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Two fixes for checks that blocked pull requests falsely once they became required.

The dash check. The required no-emdash job scanned the tracked files and the pull request's title, body and commit messages. A Dependabot body quotes upstream release notes, so a dash there turned the required check red. The job keeps its id, so the ci-required-checks ruleset needs no change, and now scans the tracked files only. A new job in the same workflow, no-emdash-messages, scans the title, body and commit messages. It is not required: it still goes red on such a body, as the prompt to edit the dash out before merging (the body becomes the squash commit), but it cannot block the merge.

Cancelled runs. pr-title.yml and no-emdash.yml ran on edited under concurrency groups that cancel. Dependabot pushes and edits at the same moment, which starts two runs, and the group cancels one; when the cancelled run sits in the newer check suite, the required context counts as failing until someone re-runs it. A group without cancel-in-progress still cancels a queued run, so both blocks are removed and every short run finishes.

Also corrected to match: CLAUDE.md's gate section, which said no-emdash scans the PR text.

Checked locally: no-emdash and claude-card from @cosyte/script-utils 0.1.4 and the commit-message scan pass, every starter passes npm ci and npm test, and actionlint 1.7.12 with shellcheck 0.11.0 is clean over every workflow.

https://claude.ai/code/session_01MXLcW95gf97vs9RBU1YsXf

…s finish

The required no-emdash job scanned the tracked files and the pull
request's title, body and commit messages. A Dependabot body quotes
upstream release notes, so a dash there turned a required check red. The
job keeps its name and now scans the tracked files only; a new job,
no-emdash-messages, scans the PR text and is not required.

The dash workflow and the PR title caller ran under concurrency groups
that cancel. A push and an edit that land together (Dependabot does both)
start two runs and one is cancelled; when the cancelled run is in the
newer check suite, the required context counts as failing until someone
re-runs it. A group without cancel-in-progress still cancels a queued
run, so both blocks are removed and every short run finishes.

The docs that described the PR-text scan or the required checks are
corrected to match.

Claude-Session: https://claude.ai/code/session_01MXLcW95gf97vs9RBU1YsXf
@NSchatz
NSchatz merged commit e053ce2 into main Nov 8, 2026
30 checks passed
@NSchatz
NSchatz deleted the ci/dash-split-pr-title branch November 8, 2026 04:46
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