fix(review): correct stale 'gittensory' brand reference in a comment - #9205
Merged
Conversation
#9173 introduced a comment referencing the deprecated pre-rename product name, which the branding-drift baseline does not account for -- breaking the branding-drift:check gate for every PR based on current main.
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
#9173 landed a comment in
src/review/predicted-gate-agreement.tsreferencing the deprecated pre-rename product name ("gittensory") instead of the current one ("loopover"). Thebranding-drift:checkgate does not have this in its recorded baseline, so it currently fails onmainfor this file and will fail CI for every PR based on current main until fixed — confirmed via a freshorigin/maincheckout.Test plan
npm run branding-drift:check— now reports ok (39 files match baseline)npx tsc --noEmit -p tsconfig.json --incremental false(after building@loopover/engine) — clean