[go: up one dir, main page]

Skip to content

Model switching for review_merge_request on DAP

What does this MR do and why?

This change adds special handling for code review workflows in an AI service. When the system is processing a "code review" workflow, it now uses a specific AI feature called "review_merge_request" instead of the default "duo_agent_platform" feature. The code also includes tests to verify that this new behavior works correctly, ensuring that code review workflows get routed to the appropriate AI model and settings. This allows the system to use different AI configurations depending on whether it's doing general AI tasks or specifically reviewing code changes.

References

Screenshots or screen recordings

Before After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #576035

Merge request reports

Loading