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

failed to deploy to github pages #1231

Open
kambing86 opened this issue Feb 1, 2021 · 1 comment
Open

failed to deploy to github pages #1231

kambing86 opened this issue Feb 1, 2021 · 1 comment
Labels

Comments

@kambing86
Copy link

kambing86 commented Feb 1, 2021

just migrated to https://www.travis-ci.com/

then found that deployment to github pages always failing

repo: https://github.com/kambing86/npm-explorer

log here: https://api.travis-ci.com/v3/job/479273759/log.txt

travis_fold:start:dpl.3
�[33mDeploying application�[0m
Initialized empty Git repository in /tmp/d20210201-7869-1ktbpic/work/.git/
Repo created successfully
Switched to a new branch 'gh-pages'
An orphan branch gh-pages created successfully
cd -
cd /tmp/d20210201-7869-1ktbpic/work
Copying /home/travis/build/kambing86/npm-explorer/build contents to /tmp/d20210201-7869-1ktbpic/work (workdir: /tmp/d20210201-7869-1ktbpic/work)...
Configuring git committer to be Deployment Bot (from Travis CI) <[email protected]> (workdir: /tmp/d20210201-7869-1ktbpic/work)
Preparing to deploy gh-pages branch to gh-pages (workdir: /tmp/d20210201-7869-1ktbpic/work)
On branch gh-pages

Initial commit

nothing to commit (create/copy files and use "git add" to track)
fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Doing the git push (workdir: /tmp/d20210201-7869-1ktbpic/work)...
Couldn't push the build to github.com/kambing86/npm-explorer.git:gh-pages

travis_fold:end:dpl.3
failed to deploy
@stale
Copy link

stale bot commented Jan 8, 2022

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@stale stale bot added the stale label Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant