Test Driven Development (TDD) is best practice and the chosen software development process for companies that take their code seriously. But what about test-driven merge control? Wouldn't it be nice to make a pull request merge depend on successful test results

Workzone's automated pull request merge control is easy and straightforward to configure by defining some simple merge conditions: For a simple merge condition all or a subset of the following criteria are AND combined to allow a merge to happen or block

Workzone pull request reviewer groups yields to the nature of every team and enterprise - people come and go and constantly move in and out of teams. Defining reviewer groups as opposed to a set of fixed pre-defined reviewers allows for smooth

Workzone pull request reviewer groups cater to the flow of every team and enterprise – people come and go and constantly move in and out of teams. Use Workzone to define reviewer groups as opposed to a set of fixed pre-defined

Workzone for Bitbucket allows you to control your SCM process, when and how changes can be pushed, and how reviewers and groups are automatically added to new pull requests. Configure pre-defined casual, mandatory and suggested reviewers and groups for pull

Workzone implements fine-grained pull request merge control per branch or branch pattern. Workzone can merge the pull request automatically when all or a percentage of reviewers have approved and/or on successful build results. Workzone can delete the source branch of