-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add Experimental Argument for UninstallPrevious in Upgrade Flow #2755
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
I need to start checking more thoroughly for typos before I push . . . |
Looks like I beat you to it, sorry! |
No apology needed :) |
7b88421
to
6cb58a5
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.
Sorry we reviewed this late as we just had our v1.4 release candidate created last week.
The change looks good. Please merge to the latest when time available. Thanks.
And an open question, since import command also converts to upgrade when needed, does power user want to remove previous for them as well? I guess not, but I'll just leave the question here.
… UninstallPreviousArg
Possibly; I think it may be best to wait and see if we get feedback on it since I'm not sure how useful it will be in the import scenario |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Left this just for the upgrade flow (and Installs that switched to using the upgrade flow). May potentially want to consider enabling for default install flow (for when --force) is used. Depends on user feedback and use cases
This will cause a merge conflict with #2733 due to the Experimental Features Enum; If pinning is merged first, I will be happy to rebase this
Microsoft Reviewers: Open in CodeFlow