First off, I would really like to commend you for caring and responding to everyone on here. You deserve a lot of kudos for this!<p>&#x27;Test the merge&#x27; is something that we already get from GitHub. Travis CI tests both the merge and the branch itself. I think it only makes sense to test both, in fact, if I were to choose one way for a Merge Request, I would just test the merge result.<p>We have IoT Platform SDKs (See <a href="https:&#x2F;&#x2F;github.com&#x2F;IOT-DSA&#x2F;sdk-dslink-dart" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;IOT-DSA&#x2F;sdk-dslink-dart</a> and <a href="https:&#x2F;&#x2F;github.com&#x2F;IOT-DSA&#x2F;sdk-dslink-java" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;IOT-DSA&#x2F;sdk-dslink-java</a> for examples) that at somepoint I would like to pitch the idea to move from GitHub to GitLab fully. We currently utilize GitLab for only a portion of our projects. We find it really helpful that Travis CI tests both the merge result and the branch, and even though I could look over it to switch GitLab (because let&#x27;s face it, GitLab &gt; GitHub), I would love to be able to tell the other developers that they will only be gaining functionality.<p>As for the code analytics, I have second guessed myself, and I completely agree with you now. This is definitely something that I see most useful in the enterprise setting.