Uh oh!
There was an error while loading. Please reload this page.
fix(desktop): reword bot.css comment — #663 contract matched its own documentation - #664
Merged
Conversation
…n doesn't match its own documentation #663's new contract bans the literal pattern in settings CSS; the explanatory comment contained it verbatim and failed the suite on main. Comment rephrased; 2285/2285 green.
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
#663 shipped with a red suite on main: the new ban-assertion greps all renderer CSS for the tag-qualified selector pattern, and the explanatory comment in bot.css contained the literal string. My verification chain used && after a grep that still matched on partial success — process bug on my side, flagged and fixed. Suite is 2285/2285 green with this.