Loading
Rename Duo Code Review depths to Lite and Standard
What does this MR do and why?
Renames the Duo Code Review depths: Deep becomes Standard and Standard becomes Lite, following the naming decision and final copy. Part of https://gitlab.com/gitlab-org/gitlab/-/work_items/639721+
Backend and frontend ship together because standard changes meaning (light before, heavy after). The commits can be reviewed separately:
- Backend: renames the flag to
duo_code_review_standard_flow, the flow tostandard_code_review(already in the AI Gateway and CustomersDot) and the model key toreview_merge_request_dap_standard. Quick action, GraphQL and REST values becomelite/standard, with no deprecation since they're experiment and beta. - Frontend: the reviewer menu, autocomplete, badges, model selection and settings use the new names.
- Lite: renames the interim name Quick to Lite.
- Copy: capitalizes Lite and Standard in quick action replies and applies the final copy.
Stored values don't change (0 is the lighter flow, 1 the heavier one), so there's no data migration. Jobs enqueued with deep before the deploy run as Standard.
Local testing
With duo_code_review_standard_flow on and the AI Gateway on main (includes gitlab-org/modelops/applied-ml/code-suggestions/ai-assist!7985 (merged)):
- A plain
/request_review @GitLabDuoon a project with the Lite default runscode_reviewon thereview_merge_request_dapmodel setting, and findings are labelledlite. /request_review @GitLabDuo -literunscode_reviewand repliesRequested a Lite review from @GitLabDuo./request_review @GitLabDuo -standardrunsstandard_code_review1.0.0 onreview_merge_request_dap_standard, labels findingsstandard, and repliesRequested a Standard review from @GitLabDuo.- With the project default set to Standard, a plain
/request_review @GitLabDuorunsstandard_code_review. - With Standard not allowed, a saved Standard default is stored as Lite, and
-standardis rejected withFailed to find users for '-standard'. - With the flag off, a requested Standard review uses
review_merge_request_dap. - A review started with the old
deepdepth, as a job enqueued before the deploy would be, runsstandard_code_review.
Screenshots
| Project settings | Group settings | Admin settings |
|---|---|---|
![]() |
![]() |
![]() |
| Sidebar re-request | Autocomplete | Model selection |
|---|---|---|
![]() |
![]() |
![]() |
| Review badge | Lite finding comment | Standard finding comment |
|---|---|---|
![]() |
![]() |
![]() |
How to set up and validate locally
- Enable
duo_code_review_standard_flowand turn on beta features for the root group. - In the project's merge request settings, check the depth shows Lite (Default) and Standard, and the checkbox says Allow Standard reviews.
- On an MR, run
/request_review @GitLabDuo -standardand check the workflow runsstandard_code_review. - Type
/request_review @GitLabDuo -and check autocomplete offers Lite and Standard. The reviewer sidebar re-request menu shows the same two options.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist.
References
Edited by Kinshuk Singh








