Last Updated: February 25, 2016
· filipekiss
1900150 10203074354438338 1015529188 n

Prevent Git merge Commits


I've found this article very interesting. It tells us to use rebase instead of merge when fetching changes from our remotes.

To learn how to do it, please refer to the article above.

Here's my 2 cents about it and why you should do it:

  1. Prevents a lot of git "useless" messages of merges.
  2. Keeps the project timeline a lot cleaner
  3. Makes easier to find the commits that really matter for the project.

This will prevent those merge messages when pulling from the remote, but will keep the message in case of a real merge :) So It's been really usefull to find exaclty where our branches merged in our projects and then revert if anything goes wrong.

Say Thanks