{"id":335,"date":"2020-08-24T16:33:01","date_gmt":"2020-08-24T14:33:01","guid":{"rendered":"http:\/\/www.myblog.nguenkam.com\/?p=335"},"modified":"2020-08-24T16:56:34","modified_gmt":"2020-08-24T14:56:34","slug":"create-a-remote-git-branch","status":"publish","type":"post","link":"https:\/\/nguenkam.com\/blog\/index.php\/2020\/08\/24\/create-a-remote-git-branch\/","title":{"rendered":"create a remote Git branch?"},"content":{"rendered":"\n

First, you create your branch locally:<\/p>\n\n\n\n

git checkout -b <branch-name> # Create a new branch and check it out<\/code><\/pre>\n\n\n\n
The remote branch is automatically created when you push it to the remote server. So when you feel ready for it, you can just do:<\/p>\n\n\n\n
git push <remote-name> <branch-name> <\/code><\/pre>\n\n\n\n
Where <remote-name><\/code> is typically origin<\/code>, the name which git gives to the remote you cloned from.Your colleagues would then just pull that branch, and it’s automatically created locally. Or they can reach your branch, by doing:<\/p>\n\n\n\n
git fetch\ngit checkout origin\/your_branch<\/code><\/pre>\n\n\n\n
Note however that formally, the format is:<\/p>\n\n\n\n
git push origin <local-branch-name>:<remote-branch-name><\/code><\/pre>\n\n\n\n
But when you omit one, it assumes both branch names are the same.Having said this, as a word of caution<\/strong>, do not make the critical mistake of specifying only :<remote-branch-name><\/code> (with the colon), or the remote branch will be deleted!<\/p>\n\n\n\n
Upstream<\/h4>\n\n\n\n
So that a subsequent git pull<\/code> will know what to do, you might instead want to use:<\/p>\n\n\n\n
git push --set-upstream origin <local-branch-name> <\/code><\/pre>\n\n\n\n
or ( Short-form)<\/p>\n\n\n\n
git push -u origin <local-branch-name> <\/code><\/pre>\n\n\n\n
As described below, the --set-upstream<\/code> option sets up an upstream branch. git sets the new branch as a remote track branch (tracking):<\/p>\n\n\n\n
 Adding a remote tracking branch means that git yet  knows what you want to do when you git fetch, git pull, or git push in the future. This assumes that you want the local branch and the remote branch  to be in sync.<\/p><\/blockquote>\n\n\n\n
it means now we can simply  write  command   (example: “git fetch” ) without any option. <\/p>\n\n\n\n
git push origin <local-branch-name> <\/code><\/pre>\n\n\n\n
can now be (short) written as :<\/p>\n\n\n\n
git push <\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
First, you create your branch locally: The remote branch is automatically created when you push it to the remote server. So when you feel ready for it, you can just do: Where <remote-name> is typically origin, the name which git gives to the remote you cloned from.Your colleagues would then just pull that branch, and it’s automatically created […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[60],"tags":[62,61,63],"_links":{"self":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/335"}],"collection":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=335"}],"version-history":[{"count":6,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/335\/revisions"}],"predecessor-version":[{"id":342,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/335\/revisions\/342"}],"wp:attachment":[{"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nguenkam.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}