Enable Duo Code Review by default on new customers namespaces

What does this MR do and why?

Enables GitLab Duo's Automated Code Review by default for new namespaces on SaaS. This change aligns with the new flat pricing model (0.25 GitLab Credits per review) and provides immediate value to new users without requiring manual setup.

This MR only implements the backend part of #592822. The banner and all other frontend communication will be implemented in a follow-up MR.

These changes are behind a feature flag and will only be enabled when the banner is available.

Implementation Details

This MR addresses the following requirements from #592822:

References

Related to #592822

Screenshots or screen recordings

Registration

Kapture_2026-03-25_at_13.40.18

Settings

Screenshot_2026-03-25_at_13.42.17

Screenshot_2026-03-25_at_13.42.47

How to set up and validate locally

  • Make sure you have CustomersDot up and running locally
  • Change your GDK customer_portal_url to use you local CDot instance
    license:
       customer_portal_url: http://127.0.0.1:5000 # was https://customers.staging.gitlab.com
       license_mode: test
  • On your GDK instance, run Gitlab::CurrentSettings.update!(allow_local_requests_from_web_hooks_and_services: true) to allow connections to your local CDot
  • Reconfigure/restart GDK to apply all changes
  • Navigate to your GDK instance and create a new account
  • Check of foundational flows enabled under Group > Settings > GitLab Duo > Change Configuration > Allow Foundational Flows (see screenshot above)
  • Check for automatic Code Review under Group > Settings > General > Merge Requests (see screenshot above)

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.

Edited by Wanderson Policarpo

Merge request reports

Loading