Approve Checker 1.1 adds a "Minimum Number of Approvers" field to the configuration page (thanks to Steven Hadfield). This option means that it is now possible to create rules which will allow the merge to proceed once approvals have been given by a subset of users in the list of approvers. If this value is set to 0 then approvals are required from all of the specified users.
Support
To learn more about the app, you should:
- Read the documentation.
Description
Supports up to 5 rules
Rules can be specified for a maximum of 5 different branches
Different approvers for different branches
Each rule specifies a branch name and an arbitrary list of users who must give their approval before pull requests can be merged to this branch.
Approvals outstanding
The pull request lists the approvals still required before it can be merged into the target branch.
More details
Approve Checker supports up to 5 separate "rules" which specify a branch name and a list of required approvers. The following actions are performed for each active rule:
- A pre-receive hook prevents any changes from being pushed directly to the specified branch.
- A merge check prevents pull requests from being merged to the target branch until the specified users have given their approval (note that the author of the pull request is considered to have implicitly approved it).
Each rule can be configured to require that all of the specified users must give their approval, or alternatively, it may require a certain number of users from the specified list to give their approval.
Version history
1.1Bitbucket Server 3.0.0 - 3.11.62014-11-05Add option to configure minimum number of approvers 1.0Bitbucket Server 3.3.0 - 3.11.62014-10-18Initial release No release notes.