Enforcing Workzone merge conditions on all levels
Workzone doesn’t stop users merging pull requests manually by clicking the ‘Merge’ button. However, if merge conditions are to be enforced this can be enabled in Workzone’s global settings, project and or repository settings. The most specific setting will be applied.
Adding specific pull request reviewers for different parts of your codebase
TL;DR Specifying include and exclude file/path patterns for pull request reviewers with Workzone makes sure that specialised teams only need to review 'their' code changes. This saves them time and reduces the pull request noise level. Too many PR reviews, every day
Workzone Project Settings – Here we go
Bitbucket Server 5.2 brought us project-wide settings for most configurable features. Now the shiny new version 5.5.0 of Workzone for Bitbucket has project-wide settings for Hooks Reviewers Digital Signature Approvals (Auto) Merge Conditions Caveat: Workzone project configurations won't let you select
Workzone Advanced Merge Conditions with Specific Group Quota
Advanced Merge Conditions with groupQuota are an important part of Workzone's merge-control features. Let's recap on advanced merge conditions: A boolean expression describes the merge condition in a clear and concise way. Using tokens like approvalQuota, groupQuota, requiredSignaturesCount, requiredBuildsCount an advanced merge condition could be
How to do test-driven development with merge control and continuous integration
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
From simple to advanced control of merge conditions
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
Benefits of general quota vs group quota
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
How reviewer groups can streamline your pull request process
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
Predefine pull request reviewers
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
Create Automatic Pull Request Merge in Bitbucket
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