Loading
Rename advanced code review flow to deep
Note
No one can use this flow yet, so this is safe to merge.
What does this MR do and why?
This MR renames the flow reference the monolith sends to the AI gateway from advanced_code_review/v1 to deep_code_review/v1, and renames the feature flag duo_code_review_advanced_flow to duo_code_review_deep_flow and every place the flag is referenced, including the frontend.
A flag rename drops its enabled state, so it needs to be re-enabled after deploy; the flag is only on for one user and dogfooding has not started, so this is the cheapest time to do it. This MR is stacked on !255442 (merged) and should merge after it, and after the AI gateway MR, since the flow id rename is a hard cutover with no alias.
Screenshots or screen recordings
N/A, backend-only change.
How to set up and validate locally
- Check out
627791-rename-code-review-flow-reference-to-deep. - Run
bundle exec rspec ee/spec/lib/ai/duo_workflows/foundational_flow_start_params_resolver_spec.rb ee/spec/services/ai/duo_workflows/code_review/process_comments_service_spec.rband the Jest specee/spec/frontend/notes/components/duo_code_review_feedback_link_spec.js. - Confirm the flag is now
duo_code_review_deep_flowin the rails console.
MR acceptance checklist
This MR meets the Definition of Done.
References
- Rename discussion: gitlab-org#23492 (comment 3833155917)
- Implementation issue: #627566 (closed)
- AI gateway MR: gitlab-org/modelops/applied-ml/code-suggestions/ai-assist!6932 (merged)
Edited by Kinshuk Singh