docs: fix review gate README anchor#436
Open
CooperSheroy wants to merge 1 commit into
Open
Conversation
rajpratham1
approved these changes
Jul 5, 2026
rajpratham1
left a comment
There was a problem hiding this comment.
This is a straightforward documentation fix with an appropriate regression test.
Review
README fix ✅
The link changes from:
to
This fixes a broken internal anchor and also updates the terminology to match the current documentation.
Regression test ✅
The added assertions verify both:
the new anchor exists
assert.match(readme, /[review gate](#enabling-review-gate)/i);
the old broken anchor is gone
assert.doesNotMatch(readme, /#what-does-the-review-gate-do/i);
This prevents future documentation regressions.
Risk
None.
Only documentation and a documentation validation test are modified.
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.
Summary
Verification
Note: an initial full
npm testrun was stopped after it appeared stuck after test 77; all emitted tests up to that point had passed. The focused docs test above passed after the change.