Skip to content

Align Rollout Doc's Own Sequence With Its Maintenance Rule #966

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ptr727 merged 1 commit into from
Aug 24, 2026
Merged

Align Rollout Doc's Own Sequence With Its Maintenance Rule #966

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/pre-commit-hooks-rollout.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ Open the PR through the repo's normal branching model.
A repo whose corpus does not yet pass its language formatter clean ships the doc-gate half first
and adds the language half once it does, per the mid-convergence carve-out. That partial state is
not a reason to leave the box unchecked, since the doc-gate half alone already satisfies
`parity.hooks`' intent tier. After merge, check the box below.
`parity.hooks`' intent tier. Check the box below in this same PR, before it merges, per the maintenance rule above.

A repo declaring neither `csharp` nor `python` in `registry/repos.json` (the `eda` repos, and any
repo with no fleet-covered language) has no language-format half to add: the doc-gate half alone
Expand Down