-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update of gh-pages fails on new pull-request #957
Comments
@keremispirli Any ideas that could help? |
On windows rebase works:
Is the issue linux specific? Did I do something wrong to try to reproduce? |
The issue is repeatable |
Why complain on |
In the current solution, So, I propose to make Actions done:
My attempt failed: it seems that my changes to gh-pages are later in the archive, so are ignored by the earlier made pull request. |
To delete a git branch remotely see: |
@keremispirli Where are the gh-pages actually used? |
What is in commit 9154a5d
|
First attempt fails:
despite
user name seems not to be set ;-( |
Currently, we have a script that is hard to test: it is only executed when A better alternative would be to have a hook that updates Maybe also look at similar concepts in other languages like java and javaDoc: https://stackoverflow.com/questions/11938270/how-i-can-move-javadoc-from-master-branch-to-gh-pages-branch-on-github-using-egi |
See how cabal handle haddock on travis-ci: Similar on travis-ci: https://chromabits.com/posts/2016/07/04/haddock-travis/ |
For better traceability, I propose to use 'set -v' in our scripts. See e.g. https://stackoverflow.com/questions/2853803/how-to-echo-shell-commands-as-they-are-executed |
See https://semaphoreci.com/torxakis-admin/torxakis/branches/develop/builds/742
The statement
if [ "$BRANCH_NAME" = "develop" ] && [ "$SEMAPHORE_TRIGGER_SOURCE" != "scheduler" ]; then git config --global user.email "semaphore@example.com"; git config --global user.name "SemaphoreCI"; ./ci/cleanup.sh; ./ci/updateAndPushGhPagesFromDevelop.sh; fi
fails with
The text was updated successfully, but these errors were encountered: