docs(standard): add CI9, the shared ADR check fetched from main - #121
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
standard.md: new CI9 · Shared ADR check. Thelintjob runsjust adr-check; the recipe text is fixed byte for byte (as RL5 does forrelease.yml); no repo keeps a copy oftests/test_adr_citations.py. The Why records the decision to trackmainunpinned and its trade, and why each pytest flag and the in-repo temp dir are there.tests/test_adr_citations.py: two-sentence note in the invariant's docstring that every repo fetches this file frommain, so nobody edits it as a local test.Why now
All 25 consumer repos (24 merged plus lite-bootstrap#266 in flight) already run exactly this recipe, so nothing needs converging. It lands as a MUST rather than as a SHOULD with a date for that reason; the SHOULD step exists to give repos time, and there is nothing left to give time to. If the process rule should be read literally anyway, changing MUST to SHOULD here is a one-word edit.
Verified
Org suite 134 passed;
mkdocs build --strictbuilds; anchor#CI9renders.