-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Closed
Milestone
Description
🐞 Bug report
Command (mark with an x
)
- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
Is this a regression?
Yes, the previous version in which this bug was not present was: ....Description
When running: `ng update @angular/cli @angular/core --next --allow-dirty`It automatically checked in the result to my git repo. This is definitely NOT desired. In many use cases, this may be a "Trial" without a desire to check in. In other use cases, this may be a key dev environment that the developers would want to try out before committing.
In any case, this should NOT automatically check in without at least asking first.
UPDATE: In looking into this further, it does THREE commits during the update process.
🔬 Minimal Reproduction
-
Run: ng update @angular/cli @angular/core --next --allow-dirty
-
Check the Git change list, all changes are check in.
🔥 Exception or Error
No error
🌍 Your Environment
Was 8.1.3 prior to the update.
Now:
Angular CLI: 9.0.0-rc.0
Node: 10.16.0
OS: win32 x64
Angular: 9.0.0-rc.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.900.0-rc.0
@angular-devkit/build-angular 0.900.0-rc.0
@angular-devkit/build-optimizer 0.900.0-rc.0
@angular-devkit/build-webpack 0.900.0-rc.0
@angular-devkit/core 9.0.0-rc.0
@angular-devkit/schematics 9.0.0-rc.0
@ngtools/webpack 9.0.0-rc.0
@schematics/angular 9.0.0-rc.0
@schematics/update 0.900.0-rc.0
rxjs 6.5.3
typescript 3.6.4
webpack 4.41.2
Anything else relevant?
Splaktar, benelliott, SanderElias, KwintenP, alyssamichelle and 2 more