Skip to content
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

docs: fix typo #27865

Closed
wants to merge 1 commit into from
Closed

docs: fix typo #27865

wants to merge 1 commit into from

Conversation

markgoho
Copy link
Contributor

@markgoho markgoho commented Dec 30, 2018

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

Does this PR introduce a breaking change?

  • Yes
  • No

@brandonroberts brandonroberts added comp: docs effort1: hours target: patch This PR is targeted for the next patch release risk: low state: community Someone from the Angular community is working on this issue or submitted this PR type: bug/fix labels Jan 4, 2019
@ngbot ngbot bot modified the milestone: Backlog Jan 4, 2019
@brandonroberts brandonroberts self-assigned this Jan 4, 2019
@IgorMinar IgorMinar added the action: merge The PR is ready for merge by the caretaker label Jan 11, 2019
Copy link
Contributor

@IgorMinar IgorMinar left a comment

Choose a reason for hiding this comment

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

Thanks!

@IgorMinar IgorMinar added the merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note label Jan 11, 2019
@IgorMinar
Copy link
Contributor

Caretaker note: legacy pullapprove check failed - please ignore.

AndrewKushnir pushed a commit that referenced this pull request Jan 11, 2019
AndrewKushnir pushed a commit that referenced this pull request Jan 16, 2019
wKoza pushed a commit to wKoza/angular that referenced this pull request Jan 18, 2019
wKoza pushed a commit to wKoza/angular that referenced this pull request Jan 18, 2019
ngfelixl pushed a commit to ngfelixl/angular that referenced this pull request Jan 28, 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 Sep 14, 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 effort1: hours merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note risk: low state: community Someone from the Angular community is working on this issue or submitted this PR target: patch This PR is targeted for the next patch release type: bug/fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants