Automatic re-review on new commits for mono-repo collaborative workflows
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
In mono-repo environments where multiple developers contribute to a single MR for features that affect multiple layers (e.g., services API, backend, frontend, DB), there's a need for automatic re-review when new commits are pushed. The concern is that new commits for one layer might adversely affect another layer, and an automatic re-review would catch these issues so they wouldn't get overlooked.
User request
@andrewtamayo asks:
are there any plans to have a setting for gitlab duo (MR reviewer) to automatically re-review MRs upon new commits to the branch without manually triggering the re-review?
Use case
This is particularly important for:
- Mono-repo collaborative workflows: Multiple developers working on different layers of the same feature in a single MR
- Cross-layer impact detection: New commits to one layer (e.g., API changes) might introduce issues in other layers (e.g., frontend, backend)
- Continuous quality assurance: Ensuring that each incremental change maintains code quality without requiring manual re-review requests
Relationship to existing work
This request relates to #507336 (Support request for changes and approvals with Duo Code Review), which includes automatic re-review as part of the broader approval workflow. However, this specific use case emphasizes the need for automatic triggering in collaborative, multi-developer scenarios.
The previously closed issue #546635 (closed) (Re-request Duo Code Review automatically when new commits are pushed) was marked as a duplicate of #507336.
Proposal
Enable automatic re-review of MRs by Duo Code Review when new commits are pushed, with:
- Configuration option: Project-level setting to enable/disable automatic re-review on new commits
- Focused re-review: Review should focus on new/changed code and verify previously identified issues haven't been reintroduced
- Multi-developer awareness: Handle scenarios where different developers are contributing to the same MR
This would complement the broader approval workflow described in #507336 while specifically addressing the mono-repo collaborative use case.
This issue was created based on customer feedback from: https://gitlab.com/gitlab-com/account-management/western-north-america/cisco-group/splunk-group/splunk-duo-sm-self-hosted-models-pov/-/issues/75