SCM Maturity
A new level maturity for your SCM process. Control the Pull Request Merge Button
Among other popular feature requests Workzone for Bitbucket introduces tighter control over the Pull Request merge-button.
Ever wondered why that merge button was ‘hot’ while the Pull Request was not ‘ready’ yet?
Approvals from valued reviewers were still missing or the ‘critical’ mass you need to sanction a merge was not reached – and that Pull Request merge-button was active; for anyone to click and merge – just like that. Although possible – everyone knows it’s a PITA to revert a merge-commit in the remote repository.
Workzone 2.4 introduces tighter merge control.
Configure in Workzone’s global settings whether or not the Pull Request merge button should be blocked when merge conditions are not met.
How does it work? You may be familiar with Workzone’s Pull Request auto-merge feature – a conditional automated merge. Conditions for an automated merge can be
- All or a percentage of reviewers must approved, all reviewers are considered
- All or a certain number of mandatory reviewers must approve, mandatory reviewers are configured individually and cannot be changed
- A successful build result message must be received from your CI server.
As soon as you enable ‘Enforce Merge Conditions’ globally the same rules apply to the Pull Request merge-button. If the (auto)merge conditions are not met, the button will be grayed out and the merge info will tell you why.
A new level maturity for your SCM process
With this great new feature your SCM process reaches a new level of maturity since you can guarantee that there are no accidental or intentional pre-mature Pull Request merges!
