origin [email protected]:your_user_name/consul.git (fetch) origin [email protected]:your_user_name/consul.git (push)
upstream [email protected]:consul/consul.git (fetch) upstream [email protected]:consul/consul.git (push) origin [email protected]:your_user_name/consul.git (fetch) origin [email protected]:your_user_name/consul.git (push)
git merge upstream/master
git merge v0.9
merge
command, there are three possible outcomes:Already up-to-date.
response. That means your fork is up to date with consul 😊👌Merge remote-tracking branch 'upstream/master' into upstream
. That means git was able to grab latest changes from CONSUL's master branch, and it can merge them without code change conflicts. Finish the commit.Automatic merge failed; fix conflicts and then commit the result.
message. That means there are conflicts between the code changes you did and the ones done on CONSUL repository since the last time you update it. That's the main reason we strongly recommend often updates of your fork (think at least monthly). Resolve merge conflicts carefully and commit them.