Skip to content

fix rebase glitch in PR #570#787

Closed
b-laporte wants to merge 1 commit into
angular:masterfrom
b-laporte:cleanup570
Closed

fix rebase glitch in PR #570#787
b-laporte wants to merge 1 commit into
angular:masterfrom
b-laporte:cleanup570

Conversation

@b-laporte

Copy link
Copy Markdown

I just realized that a code block got duplicated after my last rebase for PR #570 which just landed on master..

@googlebot

Copy link
Copy Markdown

Thanks for your pull request.

It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits.

Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name.

@googlebot

Copy link
Copy Markdown

CLAs look good, thanks!

@vicb

vicb commented Feb 25, 2015

Copy link
Copy Markdown
Contributor

seems like Travis was not triggered for this one, could you try to force push a little update ?

@b-laporte

Copy link
Copy Markdown
Author

travis seems to have issue as per traviscistatus - I will force another update in a few minutes..

@pkozlowski-opensource

Copy link
Copy Markdown
Member

Seems like Travis build is OK (see https://travis-ci.org/angular/angular/builds/52163352), it is just results are not reported back correctly....

@angular-automatic-lock-bot

Copy link
Copy Markdown

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.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants