Skip to content

chore(ci): say which rulesets require which CI contexts - #103

Merged
NSchatz merged 1 commit into
mainfrom
chore/ci-required-comments
Nov 9, 2026
Merged

NSchatz merged 1 commit into
mainfrom
chore/ci-required-comments

Conversation

@NSchatz

@NSchatz NSchatz commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Comment-only correction in .github/workflows/ci.yml. No behaviour changes and no changeset.

  • examples and documents: the comments said neither is a required context. The repository's ci-required-checks ruleset (19907924) requires both, so the comments now say so.
  • The banner: it said ci-required-checks requires four of the five ci / * contexts and that ci / verify (26, ubuntu-latest) is not required. The organization's library-required-checks ruleset (26785819) requires all five, Node 26 included, and ci-required-checks holds documents and examples. Both rulesets have bypass_actors: [].
  • The Node matrix note: same correction for Node 26, and the ruleset it names is an organization setting, so an organization admin changes it.

Checked: pnpm format:check, pnpm check:no-emdash, pnpm check:no-internal-refs, and test/node-support.test.ts (it reads this file) pass.

https://claude.ai/code/session_016orFiNW8PuZkqnC8pqqTP2

The comments in ci.yml said the documents and examples jobs are not
required contexts. The repository's ci-required-checks ruleset (19907924)
requires both. The banner and the Node matrix note also credited the
ci / * contexts to ci-required-checks and called Node 26 not required:
the organization's library-required-checks ruleset requires all five
ci / * contexts, Node 26 included. Comments only.

Claude-Session: https://claude.ai/code/session_016orFiNW8PuZkqnC8pqqTP2
@NSchatz
NSchatz merged commit b80f67f into main Nov 9, 2026
13 checks passed
@NSchatz
NSchatz deleted the chore/ci-required-comments branch November 9, 2026 01:07
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