Where I work we merge with the no fast forward option - this keeps an accurate git feature topology where merges are represented as their own commit. We've foun

Where I work we merge with the no fast forward option - this keeps an accurate git feature topology where merges are represented as their own commit. We've found it gives us the best of best worlds: adding clarity/readability to the history while avoiding problematic rebases. I haven't personally really noticed any downsides with that approach, can anyone else think of any?