Mandate Github "Squash and merge"
#7
In my opinion, merge commits can make the history very, very tangled and difficult to read, especially if attempting to bisect the history for a regression etc. Rebasing makes the history much more concise.

A mix of squash-merges and rebase-merges is probably the best solution for now.
Reply
Thanks given by:


Messages In This Thread
RE: Mandate Github "Squash and merge" - by xoft - 05-19-2016, 05:36 PM
RE: Mandate Github "Squash and merge" - by xoft - 05-19-2016, 10:02 PM



Users browsing this thread: 1 Guest(s)