Repository navigation
ci: use lightweight checks for reviewed prose changes - #43
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
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.
Prose-only guidance changes currently trigger expensive build and assurance jobs. Classify the complete change against a narrow allowlist: root AGENTS.md, CLAUDE.md, CONTRIBUTING.md and README.md, plus Markdown directly under docs/adr/. Keep applicable title, hygiene, secret and whitespace checks. Preserve required check names and report explicit prose-only results. Mixed changes, renames out of source, unknown paths, release metadata and tag/operational events retain existing full gates.
Add the explicit policy exception to AGENTS.md and regression cases for classification, real Git renames and failed comparisons. No runtime or numerical behavior changes.
Validation: workflow YAML and Python syntax checked; full remote CI is required for this workflow change. Test suites and builds are delegated to CI.