Our users want to manage the git commit themselves.
In case a number of conditions are not met the commit should not be successful.
Therefore the pre-commit hook for git repositories should have an option to configure per repository whether the webhook is blocking or not in case of returning UNSUCCESSFUL.
Customization of process support should not be in the core TeamForge product but in the webhooks used by the TeamForge product.
This way every project admin can tailor the behavior according the dedicated needs.
by: Hans T. | over a year ago | SCM
Comments
Let me explain: Git commits happen on the client side, so commit creation cannot be controlled by TeamForge.To be clear: it is possible to implement a Git pre-commit hook but it is not feasible to control it from TeamForge. But this is when code review process comes in. TeamForge already provides various mechanisms: Code review process, Review Gates and CI-verifciation, that can define conditions on which a given change can be merged or not. But it is all pre-merge rather than pre-commit.