Skip to content

docs: create migration guide for v9 hammer migration #17752

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

Merged
merged 4 commits into from
Nov 20, 2019

Conversation

devversion
Copy link
Member

No description provided.

@devversion devversion added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful docs This issue is related to documentation labels Nov 19, 2019
@devversion devversion added this to the 9.0.0 milestone Nov 19, 2019
@devversion devversion requested a review from jelbourn as a code owner November 19, 2019 15:08
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 19, 2019
@jelbourn
Copy link
Member

Here's a commit with my proposed edits
jelbourn@8ac15b1

@devversion devversion added the target: patch This PR is targeted for the next patch release label Nov 20, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one tiny nit. Add merge-ready when ready

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Nov 20, 2019
@jelbourn jelbourn merged commit 3a204da into angular:master Nov 20, 2019
@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 Dec 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement docs This issue is related to documentation P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants