I could not solve this problem so I came up with another solution: -check out a new branch called "source" which is an exact copy of "master".
-deploy the site to branch "gh-pages" with usual gh-pages npm module. (I use npm in my example, but the script is same.)
rebase "master" to "gh-pages" and simply push it. So "master" will have what "gh-pages" will have.
It is a not a clean solution though. Any feedback is much appreciated.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am having the exact same problem right now but I could not get it work. Could you please share how did you solve it?
EDIT: for anybody who would face the same problem: refer here
github.com/tschaub/gh-pages#when-g...
I could not solve this problem so I came up with another solution: -check out a new branch called "source" which is an exact copy of "master".
-deploy the site to branch "gh-pages" with usual gh-pages npm module. (I use npm in my example, but the script is same.)
It is a not a clean solution though. Any feedback is much appreciated.