-
Notifications
You must be signed in to change notification settings - Fork 85
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
keep lint in separate GitHub action #111
Comments
karfau
added a commit
that referenced
this issue
Aug 23, 2021
To fix #111 I think it's good enough to split test and lint into two different build steps. Separate actions are not required since the github actions details view now shows what steps failed. To be able to do that split, I needed to drop the execution of the `lint` script from the `test` script. The `start` script still runs both in watch mode, so it's still easy to run both when developing.
This was referenced Dec 25, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
idea from @karfau
Prettier does this, and I think it would help people see more quickly whether a build failure comes from lint or from a test failure.
The text was updated successfully, but these errors were encountered: