fix(review): correct a stray gittensory reference to loopover in a doc comment - #9204
Merged
Merged
Conversation
…c comment Trips the branding-drift check, which was already red on main independent of any other change -- a one-word rename leftover in a comment.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
❌ 5 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
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
src/review/predicted-gate-agreement.tstripsbranding-drift:check-- confirmed already failing onmain's own HEAD (independent of any other in-flight PR).computeGateParity's own doc comment (src/review/parity.ts) already uses for the same comparison ("reviewbot->loopover convergence").Scope
type(scope): short summaryConventional Commit format.CONTRIBUTING.mdand does not reintroduce GitHub Pages, VitePress,site/, orCNAME.Validation
git diff --checknpm run branding-drift:check(was failing, now passes: "39 file(s) match the recorded baseline")npx vitest run test/unit/predicted-gate-agreement.test.ts test/unit/check-branding-drift-script.test.ts(39 tests, all pass)test:cisteps not run locally -- comment-only change with zero behavior impact, no source logic touched.Safety
Notes
validate/validate-codeon every open PR (confirmed onmain's own latest commit's check-runs), including fix(review): serialize public-surface publish under the per-PR actuation lock (#9013) #9181 -- unrelated to that PR's own diff.