Git - What is the difference between push default matching and simple

Question

I have been using git for a while now  but I have never had to set up a new remote repo myself and I have been curious on doing so  I have been reading tutorials and I am confused on how to get  git push  to work    If I simply use git push it asks me to see up a default branch    to point to  What is the difference between these two options it supplies me with   git config --global push default matching git config --global push default simple   Matching just pushes whatever branches I have on my local repo  and if they don t match I have to then manually tell it to push whatever new local branches I have  correct  Is this best practice to use or is simple best

User · Answer

Git v2 0 Release Notes  Backward compatibility notes  When git push   there  does not say what to push  we have used the traditional  matching  semantics so far  all your branches were sent to the remote as long as there already are branches of the same name over there    In Git 2 0  the default is now the  simple  semantics  which pushes    only the current branch to the branch with the same name  and only when the current branch is set to integrate with that remote branch  if you are pushing to the same remote as you fetch from  or only the current branch to the branch with the same name  if you are pushing to a remote that is not where you usually fetch from    You can use the configuration variable  push default  to change this   If you are an old-timer who wants to keep using the  matching  semantics  you can set the variable to  matching   for example   Read the documentation for other possibilities   When git add -u and git add -A are run inside a subdirectory without specifying which paths to add on the command line  they operate on the entire tree for consistency with git commit -a and other commands  these commands used to operate only on the current subdirectory    Say git add -u   or git add -A   if you want to limit the operation to the current directory   git add  lt path gt  is the same as git add -A  lt path gt  now  so that git add dir  will notice paths you removed from the directory and record the removal   In older versions of Git  git add  lt path gt  used to ignore removals   You can say git add --ignore-removal  lt path gt  to add only added or modified paths in  lt path gt   if you really want to

User · Answer

From GIT documentation  Git Docs  Below gives the full information  In short  simple will only push the current working branch and even then only if it also has the same name on the remote  This is a very good setting for beginners and will become the default in GIT 2 0  Whereas matching will push all branches locally that have the same name on the remote   Without regard to your current working branch     This means potentially many different branches will be pushed  including those that you might not even want to share   In my personal usage  I generally use a different option  current which pushes the current working branch   because I always branch for any changes    But for a beginner I d suggest simple     push default   Defines the action git push should take if no refspec is   explicitly given  Different values are well-suited for specific   workflows  for instance  in a purely central workflow  i e  the fetch   source is equal to the push destination   upstream is probably what   you want  Possible values are       nothing - do not push anything  error out  unless a refspec is   explicitly given  This is primarily meant for people who want to avoid   mistakes by always being explicit       current - push the current branch to update a branch with the same   name on the receiving end  Works in both central and non-central   workflows       upstream - push the current branch back to the branch whose changes   are usually integrated into the current branch  which is called     upstream    This mode only makes sense if you are pushing to the   same repository you would normally pull from  i e  central workflow        simple - in centralized workflow  work like upstream with an added   safety to refuse to push if the upstream branch s name is different   from the local one       When pushing to a remote that is different from the remote you   normally pull from  work as current  This is the safest option and is   suited for beginners       This mode will become the default in Git 2 0       matching - push all branches having the same name on both ends  This   makes the repository you are pushing to remember the set of branches   that will be pushed out  e g  if you always push maint and master   there and no other branches  the repository you push to will have   these two branches  and your local maint and master will be pushed   there        To use this mode effectively  you have to make sure all the branches   you would push out are ready to be pushed out before running git push    as the whole point of this mode is to allow you to push all of the   branches in one go  If you usually finish work on only one branch and   push out the result  while other branches are unfinished  this mode is   not for you  Also this mode is not suitable for pushing into a shared   central repository  as other people may add new branches there  or   update the tip of existing branches outside your control       This is currently the default  but Git 2 0 will change the default to   simple

User · Answer

git push can push all branches or a single one dependent on this configuration  Push all branches git config --global push default matching  It will push all the branches to the remote branch and would merge them  If you don t want to push all branches  you can push the current branch if you fully specify its name  but this is much is not different from default  Push only the current branch if its named upstream is identical git config --global push default simple  So  it s better  in my opinion  to use this option and push your code branch by branch  It s better to push branches manually and individually

[git] Git - What is the difference between push.default "matching" and "simple"

Git v2.0 Release Notes

Backward compatibility notes

Examples related to git

Examples related to git-push

Examples related to git-remote