Update policy for accessing code suggestions
What does this MR do and why?
- We are beyond the "service start date" of Feb 15
- logic previously was different for gitlab.com and self-managed but now every instance follows the same logic, which is that the user must be assigned a gitlab duo pro add-on seat
- group-level code suggestions setting no longer relevant, see #432282 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
How to set up and validate locally
- user in a gitlab instance with the code suggestions license (premium or ultimate) who is assigned a duo pro add-on seat should be able to use code suggestions