-
Notifications
You must be signed in to change notification settings - Fork 10.4k
chore: Move pre-commit commands to pre-push #17996
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
Graphite Automations"Add foundation team as reviewer" took an action on this PR • (12/04/24)1 reviewer was added to this PR based on Keith Williams's automation. "Add ready-for-e2e label" took an action on this PR • (12/04/24)1 label was added to this PR based on Keith Williams's automation. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 2 Skipped Deployments
|
E2E results are ready! |
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.
Looks good to me, only takes 1-2s for me which confused me a little but apparently it takes a while for others.
This reverts commit f63c06d.
What does this PR do?
Our commits take around 4s to complete right now. Instead of having these commands on pre-commit, we'll now have them on pre-push to improve DX.
On a side note, I noticed that all yarn commands in our monorepo have a delay of a few seconds to even startup. I moved the app-store-cli out of the monorepo as a test and running
yarn app-store:build
takes 1.2s total instead of 4s like in the mono repo. Will continue researching that further.Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
lint-staged
or in the app store build and ensure the push is blocked.