The scenario is common: You finish the changes on a codebase, all commits are ready to be pushed. You run git push and an unexpected message appears: “! [rejected]”. The reason: “Updates were rejected because the tip of your current branch is behind its remote counterpart. Integrate the remote changes (e.g. hint: ‘git pull …’) before pushing again.”.

You follow the message and run git pull. Instead of pulling all changes to your local machine you are asked to confirm a merge commit message…

Read more >