Skip to content
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

ESLint: Fail CI if there are warnings #2847

Merged
merged 2 commits into from
Apr 17, 2021

Conversation

RunDevelopment
Copy link
Member

I went through the old ESLint PRs and remembered that @LeaVerou wanted stylistic issues to be warnings. Since warnings won't fail the CI and converting warnings to errors isn't easy, I used the --max-warnings options. The CI will now fail if there are any warnings.

@github-actions
Copy link

github-actions bot commented Apr 3, 2021

No JS Changes

Generated by 🚫 dangerJS against f60cd80

@RunDevelopment RunDevelopment merged commit bb1eca9 into PrismJS:master Apr 17, 2021
@RunDevelopment RunDevelopment deleted the eslint-warn-to-error branch April 17, 2021 20:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant