On Fri, Apr 6, 2012 at 12:45 PM, Thomas Müller <[email protected]> wrote: > - on each commit/push
i think the important part is to do it /before/ each commit to master. i.e. if you commit stuff to a branch, you're allowed to break tests, but you just configure git to only accept merges whose tests pass. that way it's the responsibility of the person committing new code to not create any regressions on existing functionality. in case of conflict, the already existing master should be kept, not the new commit. cheers, Michiel _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
