Re: To decide whether merge should be done or not

2014-02-17 Thread Reshma Babu
Guten Tag Thorsten, > Than you have to execute the merge and deal with all maybe occuring > conflicts or what codebase do you want to check the quality off? If > it's the codebase after the merge you need to run the merge, if it's > something other you need to do something else and check that.

Re: To decide whether merge should be done or not

2014-02-17 Thread Reshma Babu
Hi Arwin, I do agree on manually running this scripts. However, We want to ensure a strict merge check-in policy. That is, Only clean code can be merged & committed to the repo. So, I want to ensure the script must be run compulsorily regardless, whether it is opted by the developer or not. Hope u

Re: To decide whether merge should be done or not

2014-02-17 Thread Thorsten Schöning
Guten Tag Reshma Babu, am Montag, 17. Februar 2014 um 13:35 schrieben Sie: > I need to check the code quality of the codebase before merge. That's what server side pre commit hooks are for because you can only merge already committed changes and those committed changes should have passed your qua