Skip to content

github-pages:deploy failing after first creating repo #3385

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

Closed
rolyatsats opened this issue Dec 4, 2016 · 1 comment · Fixed by #3386
Closed

github-pages:deploy failing after first creating repo #3385

rolyatsats opened this issue Dec 4, 2016 · 1 comment · Fixed by #3386

Comments

@rolyatsats
Copy link
Contributor

The function cleanGhPagesBranch() is failing due to my prior sloppiness. It is running git rm -r with no file arguments, because there are none immediately after creating.

For that I must apologize. The fix is coming right up.

rolyatsats added a commit to rolyatsats/angular-cli that referenced this issue Dec 4, 2016
Catches the error as they are no files to clean up on repo create.

Closes angular#3385
rolyatsats added a commit to rolyatsats/angular-cli that referenced this issue Dec 7, 2016
Catches the error as they are no files to clean up on repo create.

Closes angular#3385
hansl pushed a commit that referenced this issue Dec 7, 2016
Catches the error as they are no files to clean up on repo create.

Closes #3385
MRHarrison pushed a commit to MRHarrison/angular-cli that referenced this issue Feb 9, 2017
Catches the error as they are no files to clean up on repo create.

Closes angular#3385
@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.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant