Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Description
Currently the only way I can find to require approvals is to define a set of "default reviewers" and require a certain number of approvals from that group. Where this doesn't work for us is we'd like to programmatically (e.g. via bamboo making rest API calls) determine what approvals are actually relevant.
For example, our repo has subfolderA and subfolderB. If any files under subfolderA are modifed, I want to add the reviewer group A and require at least 1 approval from them. But if only files under subfolderB are modified, groupA's approval is neither needed or relevant but instead I need group B's approval.
Essentially what I'd like is an ad-hoc per-pullrequest definition of default reviewer groups configurable via REST API