janmoesen/tilde — comment on commit 22379346f5e7c0ce974602a0ad1df53eb0969307
File: .gitconfig line 39
By janmoesen:

I used to think so, but then either the default behaviour changed or (more likely) I started using more branches. When doing `git push` without further arguments, it tries to push all known branches. This often results in unexpected rejections: where I thought only `master` would get pushed, Git tried to push other branches, too, but was unable to because they had already been changed on the remote side:

$ git push
To example:src
! [rejected] example-module -> example-module (non-fast-forward)
! [rejected] fix-foobar-widget -> fix-foobar-widget (non-fast-forward)
! [rejected] subnav_hack -> subnav_hack (non-fast-forward)
! [rejected] threepointo -> threepointo (non-fast-forward)
error: failed to push some refs to 'example:src'
To prevent you from losing history, non-fast-forward updates were rejected
Merge the remote changes (e.g. 'git pull') before pushing again. See the
'Note about fast-forwards' section of 'git push --help' for details.