[UI POLISH] Fix Padding on Model Configuration Pages
What does this MR do and why?
Makes padding improvements across the Model Selection and Duo self-hosted pages
Screenshots or screen recordings
Model Configuration/Duo self-hosted
Remove extra padding and line break at top of page:
| Before | After |
|---|---|
![]() |
![]() |
Add padding to end of page:
| Before | After |
|---|---|
![]() |
![]() |
Model Selection
Add padding to end of page:
| Before | After |
|---|---|
![]() |
![]() |
How to set up and validate locally
Set-up
- An active online cloud or legacy, Ultimate license.
To validate Model Selection page (.com):
- Start GDK in saas mode
GITLAB_SIMULATE_SAAS=1 gdk start - Enable the
ai_model_switchingfeature flag by visitinghttp://gdk.test:3000/rails/features/ - Run the Duo setup rake task
GITLAB_SIMULATE_SAAS=1 bundle exec 'rake gitlab:duo:setup'to seed DB with a Duo test group (it will be calledgitlab-duo). - Visit the test group's model selection page i.e
http://gdk.test:3000/groups/gitlab-duo/-/settings/gitlab_duo/model_selectionand validate padding looks like "After" screengrabs
To validate Model Configuration/Duo self-hosted pages (self-managed):
- Start GDK in SM mode
GITLAB_SIMULATE_SAAS=0 gdk start - Enable the
ai_model_switchingfeature flag by visitinghttp://gdk.test:3000/rails/features/ - Run the Duo setup rake task
GITLAB_SIMULATE_SAAS=0 bundle exec 'rake gitlab:duo:setup'to set up with an enterprise add-on - Visit the model configuration page i.e
http://gdk.test:3000/admin/gitlab-duo/self_hostedand validate padding looks like "After" screengrabs
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.





