Skip to content

Remove ng update and ng init #4416

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.

Sign up for GitHub

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

Jump to bottom
Closed
filipesilva opened this issue Feb 3, 2017 · 2 comments
Closed

Remove ng update and ng init #4416

filipesilva opened this issue Feb 3, 2017 · 2 comments
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Comments

@filipesilva
Copy link
Contributor

We should remove these commands around the time of RC.0 since there should be no breaking changes.

Any breaking changes that may arise should instead have human-written migration notes.
@filipesilva filipesilva added the P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful label Feb 3, 2017
@Meligy Meligy mentioned this issue Feb 6, 2017
Closed
This was referenced Feb 9, 2017
Closed
Closed
@Brocco Brocco assigned Brocco and unassigned hansl Feb 10, 2017
@hansl
Copy link
Contributor

hansl commented Feb 12, 2017

Fixed in #4628

@hansl hansl closed this as completed Feb 12, 2017
@Meligy Meligy mentioned this issue Feb 15, 2017
Closed
@chenby chenby mentioned this issue Oct 10, 2018
Closed
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hansl @Brocco @filipesilva