and thus was very likely not tested as committed that is an argument that can be resolved - hereby yielding staging a nice way of creating clean commits. The d

and thus was very likely not tested as committed that is an argument that can be resolved - hereby yielding staging a nice way of creating clean commits. The developper should simply build/unittest at least the project(s) directly involved in the commit. Apart from that, the CI system should take care of the rest. es if you consider git as a standalone tool your argument makes sense, but how often is git used like that, and not as a part of a complete build/test system?