If you have used GitHub, you must have already been familiar with
I don't like have different code base from the pages branch, so in my projects,
For a very long time, I had to do with these commands as follow in order to update that branch:
It was just plain silly of me. I did google for it, but not RTFM, I didn't get any useful results, probably used wrong keywords. I finally found the correct answer with correct search keywords, here is the answer:
Here is from manpage git-push:
Well, it's all in the manual and I was actually using a shorthand by omitting the <dst>. It's good to know.
So what if you try to omit <src> part? (I am glad I already know about this. Hehe, I am bad!)
gh-pages
branch.I don't like have different code base from the pages branch, so in my projects,
master
== gh-pages
, and many of projects are doing the same. If you have documents like library reference which is generated by source, then you probably will use different base.For a very long time, I had to do with these commands as follow in order to update that branch:
git checkout gh-pages git pull . gh-pages git push git checkout master
It was just plain silly of me. I did google for it, but not RTFM, I didn't get any useful results, probably used wrong keywords. I finally found the correct answer with correct search keywords, here is the answer:
git push origin master:gh-pages
Here is from manpage git-push:
<refspec>... The format of a <refspec> parameter is an optional plus +, followed by the source ref <src>, followed by a colon :, followed by the destination ref <dst>. It is used to specify with what <src> object the <dst> ref in the remote repository is to be updated. [...] The <dst> tells which ref on the remote side is updated with this push. Arbitrary expressions cannot be used here, an actual ref must be named. If :<dst> is omitted, the same ref as <src> will be updated.
Well, it's all in the manual and I was actually using a shorthand by omitting the <dst>. It's good to know.
So what if you try to omit <src> part? (I am glad I already know about this. Hehe, I am bad!)
git push origin :remote-branch
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.