It makes your setup easier for others to understand and for you to transfer information that you read in documentation, on Stack Overflow, or in blogs.Ī common reason to add a second remote is when you have done a “fork and clone” of a repo and your personal copy (your fork) is set up as the origin remote.Įventually you will want to pull changes from the original repository. To push the branch or you can say to push the changes in the branch to the Github repo you have to run this command git push origin Sidebar on nicknames: there is a strong convention to use origin as the nickname of your main remote.Īt this point, it is common for the main remote of a repo to be hosted on GitHub (or GitLab or Bitbucket). It creates a new branch with the specified name and then checks. Note: when you add a remote you give it a nickname (here happygit), which you can use in git commands in place of the entire URL. We can use the git-checkout command with the -b option to create a new branch. Use git remote add to add a new remote: git remote add happygit To checkout from remote git branch you have to make your local system aware of remote branches by fetching the remote branches to your local system and setting. However, after the initial clone, it is often useful to add additional remotes. usage: git remote add Test the Remote git remote show->Display the remote name git remote -v->Display the remote branches. Git clone automatically adds a new remote, so often you do not need to do git init:- This will make the local folder as Git repository, Link the remote branch:- Now challenge is associate the local git repository with remote master branch. First, you must create your branch locally git checkout -b yourbranch After that, you can work locally in your branch, when you are ready to share the branch, push it.
0 kommentar(er)
