-
-
Notifications
You must be signed in to change notification settings - Fork 195
Add --yes flag to recipes:install command to overwrite all files without asking #963
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
Note that this default should impact only files for which git cannot give us the modified state or untracked files. Existing files created by recipes are supposed to be tracked files. What is your workflow in which no files are being overwritten ? |
93736e2
to
a609fb9
Compare
We have many customers that don't use Git (yes it's bad). Therefore they can't use the recipes:update command, so we tell them to use As no file is tracked, flex asks for like 30 files this question, and for non interactive sessions, it did no changes as the default was false |
Did you try using the |
I'd rather handle this with a new command line argument instead, so that the default is safe. eg Please rebase to target 2.x also (and revert the unrelated changes while doing so) |
I will add an flag |
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.
Some nitpicking and GTM
test case failing though |
is now finally green :) |
Thank you @shyim. |
When I run
recipes:install --reset --force -n
no files are overwritten, as the default as been set to false.There is currently also no way to accept that, so I changed it back to
true