Clarify 'GitLab' term in signup error message
What does this MR do and why?
Clarify 'GitLab' term in signup error message
When allow_single_sign_on option is true, new users can't signup in
using the SSO button without first having an account the current
instance. They need first to create an account in the current instance
and then link the account with the external provider.
For self-managed instances, we would like to clarify the difference
between GitLab.com account and GitLab account (this one refers to
the current instance).
Changelog: changed
Closes #415478 (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
gdk.test:3443 will be replaced by code.videoland.org or gnome.org/gitlab, for example.
| Before | After |
|---|---|
![]() |
![]() |
How to set up and validate locally
- On
gitlab.yml, set upallow_single_sign_ontofalseand restart the instance.
omniauth:
allow_single_sign_on: false # It means that signing in using your OmniAuth provider account is only allowed if the user has a pre-existing account in the current instance.
- Use
GitLab.comto signup.

