-
Notifications
You must be signed in to change notification settings - Fork 427
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
feat(cli): respect --no-auto-updates flag
in CLI config
#7396
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
27653a4
to
a332dd1
Compare
--no-auto-updates flag
in CLI config--no-auto-updates flag
in CLI config
Component Testing Report Updated Aug 20, 2024 8:22 PM (UTC) ✅ All Tests Passed -- expand for details
|
a332dd1
to
26dd321
Compare
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.
Changes makes sense to me, thanks!
Left a comment about unit test which would be good to add
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! Thanks!
* feat: respect no-auto-updates flag in cli config * test: add unit tests
Description
As auto-updates become the new "default" way to build and deploy studios, we should ensure we're offering ways to easily override default behavior. This PR adds a helper function used in the build and deploy functions that prioritizes CLI flags first, then
sanity.cli.{ts|js}
parameters, and then finally a default (which we can easily change).What to review
The new file -- does it belong in utils (it was a bit hard to place since it was shared by two different actions)?
Ways to test I may have missed? (see below)
Testing
This function is quite simple and goes through several layers of abstraction -- I'm not sure if it's particularly useful to test on its own. It would be ideal to test the
--no-auto-updates
command line input, but I'm not sure it's possible. An integration test with the flags and a cliConfig context is also not particularly useful, because we have to mock the build action in our current tests.In lieu of that, please find a recording of the various options and configuration.
--no-auto-updates.flag.small.mov