-
Notifications
You must be signed in to change notification settings - Fork 78
[RFC] Change yarn test
to run all types of checks that CI would also run
#934
Comments
In the past we would have had a task like |
I think this is a good idea but in my experience, sometimes |
@sarahscott To be fair, isn’t that because you maybe don’t have the git commit hook setup to automatically run the linter/prettier? |
Yes! 🙌 I agree whole heartedly |
@sarahscott Maybe there’s a way to also run prettier and rather than write changes exit with a failure status? If so, then that could be added to the |
@alloy I ran prettier and linter manually, so it wouldn't have been related to a git hook. |
@sarahscott Next time that it happens, try to nail down how that discrepancy could’ve occurred and then let’s fix it permanently. |
No strong opinion, I've been using |
This repo is behind culturally in how we manage git hooks - #905 In Danger and Peril I run all of the tests/linters before a push, Emission should do this too. Considering how easy/fast it is to run this stuff and how much time it takes to get that eventual feedback after the PR then CI results. |
Yep |
tracked in Jira https://artsyproduct.atlassian.net/browse/IN-15 |
More than once I have pushed code where I forgot to run one of the various test tasks. So rather than
yarn test
being a synonym foryarn jest
, we can have it doyarn type-check && yarn lint && yarn relay && yarn jest
. Thoughts?The text was updated successfully, but these errors were encountered: