#GIT SET UPSTREAM LOCAL BRANCH CODE#

Remember, though, that this is only a local setup, so if you push this branch to your primary repository, others won't have their copies of the deployment branch configured to use the second remote automatically. You can repeat this process for any number of branches, making it a great method to keep track of multiple remotes. Git branch -set-upstream-to=deployment/master Then, you can set the upstream for the current branch by running: You can create a branch with checkout -b:

#GIT SET UPSTREAM LOCAL BRANCH CODE#

The best way to handle this in git is to create another branch for code pushed to the second upstream, such as deployments to AWS CodeCommit. Really, if you're using a two remote setup, you'll probably want a better way to manage pushing code to your second remote. This is the simplest setup, however, it requires you to either pass the remote name as an argument, or switch the remote every time. Or, switch the default remote using -set-upstream: It's a hosted git repository, and has many integrations with their EC2 compute platform, enabling for automated code deployments to your servers, directly from source control. Why would you want two remotes? Well, a good use case is AWS's CodeCommit. If you have multiple remotes, they'll show up here, too.īut just because origin is the default remote, it doesn't mean you're limited to one. This will probably display the URL of your main repository on GitHub or whatever service you're using. Whenever you clone a new repository, the default remote is set as 'origin.' You can find the remotes for any given git repo by running: You could clone that endpoint and switch to a new remote without much issue.

Hopefully, you're all using the same remote and everything syncs up, but the remote is just an endpoint. u , -set-upstream-to Set up s tracking information so is considered s upstream branch.

Please note that defining an upstream for a local branch might fail if the remote you want to set upstream to has not already been fetched locally. Your local git repo is entirely yours-it isn't affected by other people's code until they push their commits to the remote. Note: if you want to push/pull by default to heroku/master from your develop branch, you can configure it with: git branch -set-upstream-to develop heroku/master You can check your merge policy on the develop branch with a: git config Note: As commented by Animay, since Git 1. The former option was deprecated in favor of the latter in git v1.8.0. The 'remote' for a branch is a URL from where your local git repo fetches changes.

Git set upstream local branch