After creating the branch "new_feature" you will have a state like
o <master> <origin/master> <new_feature> most recent commit | ...
Then, after making changes to your local branch, your repository will look like
o <new_feature> your last commit | o your first commit | o <master> <origin/master> most recent commit | ...
Performance
git pull --rebase origin master
as Cupcake suggests, you're done with
o <new_feature> your last commit | o your first commit | o <origin/master> something meanwhile commited on remote master | o <master> most recent commit | ...
your changes are rebuilt on top of "origin / master". These are not your initial commits, but they make changes to match the โnewโ โorigin / masterโ.
When reinstalling, you may get merge conflicts, because changes made on the remote host may conflict with your changes.
But since "new_feature" is now "on top" of "origin / master", you can click on the remote master.
This will also move the tag "origin / master" to the level of "new_feature". If you also want your local master to be on the go, you should check it and merge with origin / master.
source share