Keep gh-pages up to date with a master branch

Sync gh-pages + master branches

// Reference: http://lea.verou.me/2011/10/easily-keep-gh-pages-in-sync-with-master/

$ git add .
$ git status // to see what changes are going to be commited
$ git commit -m 'Some descriptive commit message'
$ git push origin master

$ git checkout gh-pages // go to the gh-pages branch
$ git rebase master // bring gh-pages up to date with master
$ git push origin gh-pages // commit the changes
$ git checkout master // return to the master branch

Thanks for this code snippet!

Here is an alias to run after git push origin master. Place this in your .gitconfig, mine is located in ~/Users/danielstepanov/.gitconfig

[alias]
	sync-ghpages = !git checkout gh-pages && git rebase master && git push origin gh-pages && git checkout master

Once added, you can run git sync-ghpages and it will automatically do the second half of the above code. I'm extremely lazy.

thanks a lot :)

It worked! Thanks a lot.

Amazing.

I looked into one of my projects again having gh-pages. Noticed that, now github provides direct publishing of master branch. index.htm should be there in master branch root folder. No more gh-pages needed.
For eg.- in repo https://github.com/PalashBansal/Collision
http://palashbansal.github.io/Collision gets updated on any change commited in master branch. gh-pages is left unused.
To set this-
Go to your repo settings, under GitHub Pages > Change Source under - Your GitHub Pages site is currently being built from the master branch. to master branch. You can even select the folder in your root folder- master branch / docs folder

^^ Thank you Palash!!! Life changing...

https://help.github.com/en/github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site

You are a life saver !!! Thanks a lot :)

You guys don't need to push the whole updates to gh-pages and even to master for updating your site. If you want to see updates on your git page, then just wait for a few minutes after "npm run deploy" on the master branch. Then, it'll be updated as you expect.

Still useful. Thanks!

Thank you very much!

Charm

You guys don't need to push the whole updates to gh-pages and even to master for updating your site. If you want to see updates on your git page, then just wait for a few minutes after "npm run deploy" on the master branch. Then, it'll be updated as you expect.

This worked for me!!!! Thank you!!!!

@PalashBansal, I published my page using docs folder in the master branch. I made some changes and pushed it successfully in my repository but the page is not updated. Any info on how to solve this problem?

@PalashBansal, I published my page using docs folder in the master branch. I made some changes and pushed it successfully in my repository but the page is not updated. Any info on how to solve this problem?

@chimepalden You need to wait for a while(around a minute to have change reflected), if still not working, I can help better by looking into reporsitory. Please share if it's not private.
If already solved, please let us know the issue and how it got resolved.
Thanks :)

// Reference: http://lea.verou.me/2011/10/easily-keep-gh-pages-in-sync-with-master/

$ git add .
$ git status // to see what changes are going to be commited
$ git commit -m 'Some descriptive commit message'
$ git push origin master

$ git checkout gh-pages // go to the gh-pages branch
$ git rebase master // bring gh-pages up to date with master
$ git push origin gh-pages // commit the changes
$ git checkout master // return to the master branch

i did this was able to push to gh-pages but the new updates is not relecting.

what else can i do here?

Hi there, why i've this one ?

git push origin gh-pages
To https://github.com/EvroHQ/MVMT
! [rejected] gh-pages -> gh-pages (non-fast-forward)
error: failed to push some refs to 'https://github.com/EvroHQ/MVMT'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

@EvroHQ
I'm having the same issue, Did you fix it?

I suggest after Line 9 of OP:
git rebase --continue

before writing
git push origin gh-pages

thank you!

Thanks!

Thanks a lot

Amazing 🥳 🎉

Thank you.
It's working fine.

You guys don't need to push the whole updates to gh-pages and even to master for updating your site. If you want to see updates on your git page, then just wait for a few minutes after "npm run deploy" on the master branch. Then, it'll be updated as you expect.

This worked for me!!!! Thank you!!!!

@S-Philp This works perfectly. Thank you.

Thank you! 🙏🙏🙏

Thanks alot for this, exactly what am looking for🙏🏾

for some reason all my components got erased by doing so :/ any solution by anyone to restore them?

thanks a lot

Thank you!

it worked! THANK YOU sooooo MUCH

Thank you!!!