-
Notifications
You must be signed in to change notification settings - Fork 12k
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
ng github-pages:deploy left the localproject on gh-pages branch #1259
Comments
You have to add the
|
@cre8 I don't want to push to master. I wanted to push to normal gp-pages branch. When it works , this commend brings back to master branch. But when it fails , it left my project directory at gp-pages branch. PS: I got email from github with title "[xmlking/parking] Page build failure". May be github had issues at that time. |
@xmlking you're right, the command shouldn't leave your repo in the wrong branch. Will investigate. |
If github-pages:deploy fails due to 'No changes found' or fails pushing to git repo, it then attempts to checkout the initial branch. Closes angular#3030 Closes angular#2663 Closes angular#1259
If github-pages:deploy fails due to 'No changes found' or fails pushing to git repo, it then attempts to checkout the initial branch. Closes angular#3030 Closes angular#2663 Closes angular#1259
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
ng --version
. If there's nothing outputted, pleaserun in a Terminal:
node --version
And paste the result here.
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
The log given by the failure. Normally this include a stack trace and some
more information.
Mention any other details that might be useful.
After running
ng github-pages:deploy --message "Optional commit message"
command with no changes to code base, my local project is left on gh-pages branch. it should leave on master branch.The text was updated successfully, but these errors were encountered: