Workzone: Order reviewer and merge rules by priority
Workzone now supports rule ordering for pull request reviewer, signature approval and merge rules. Rules are matched in order against a pull request. The first matching rule is executed. To re-arrange the order of rules in the list, click the
Welcome to Workzone Cloud Subscription
Soon, a new Workzone for Bitbucket Cloud update will be released, introducing a new payment gateway where teams of 5 or more can purchase a monthly or yearly membership.
Say hello to Workzone’s new ‘Start’ page
Starting out with Workzone has just gotten a lot easier. Workzone settings pages now features a 'Start' page where new and experienced users can find Walk through tutorials for all configuration aspects Helpful links to documentation and support. Suggestions for
First things first – merging pull requests in order
When it comes to getting the next release out and deployed - more often than not things don’t go as smooth as you wish. There’s a last-minute bugfix and another feature just got finished, plus there is a bug in
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