-
Notifications
You must be signed in to change notification settings - Fork 6.8k
build: stylelint not working correctly #20737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Recently we changed the names of some Stylelint rules, but the linter wasn't updated which leads to several warnings for each file that goes through it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
We should also make this error exit with a non-zero code
I don't think we can do much about the exit code, it's just what Stylelint decided to exit with. |
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
@crisbeto played with it for a second and found how the way to set it to fail if these things are found. Pushed it up as a fixup. |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) ℹ️ Googlers: Go here for more info. |
Nice! I don't know whether we handle fixup commits in this repo though. |
* build: styleling not working correctly Recently we changed the names of some Stylelint rules, but the linter wasn't updated which leads to several warnings for each file that goes through it. * fixup! build: styleling not working correctly Co-authored-by: Joey Perrott <josephperrott@gmail.com> (cherry picked from commit 6dfa28c)
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Recently we changed the names of some Stylelint rules, but the linter wasn't updated which leads to several warnings for each file that goes through it.
For reference, Stylelint logs the following on the CI as well, but we didn't notice because it exits with a non-error code.