On 07/10/2021 16:51, Uwe Brauer wrote: >> The inconvenience is that you need to remember to create your local branches >> using that convention (and rename current branches - which is easy to do by >> using the `git branch -M` command). > I admit I am confused: I thought I should use the same name as in > remote, so master should be master and not pub_master > > Most likely there is something fundamental I don't understand. Yes, it's easy to be confused.
There is NO requirement that the names match. There is no requirement that you even have a local branch that 'tracks' (is a duplicate of) a remote branch you are interested in - This one is really hard to grasp for newer users who weren't there when 'remotes' were invented. You simply, already, have a branch `remote/branch` that is your own local copy of that truly remote server's branch, and you can use that name when you start your feature branch. Like wise, you can use that separation of naming to distinguish your 'keep-local' branches, from your 'happy-to-publish' branches. Philip Git, juggling chainsaws while running in flip-flops ;-) -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/77d45a5e-658a-4813-d934-d14e434e26a0%40iee.email.
