Posted on 06/11/26 02:39 am
GitLab asks for a phone number to confirm you are a real person and to protect your account. A real mobile number works best; many internet (VoIP) numbers are refused. Here is how it works and what to do when the code does not come.
GitLab.com may ask new users to verify a phone number or a card before they can run CI/CD pipelines on shared runners. Developer and cloud platforms check phone numbers to keep out abuse of free resources and to protect accounts that can run up bills.
| Number type | Example | Usually accepted by GitLab |
|---|---|---|
| Your own mobile number | The SIM in your phone | Yes |
| Non-VoIP number | A carrier mobile line used once for you | Yes, in most cases |
| VoIP number | Numbers from calling apps | Often refused |
| Public free number | Receive-SMS websites | Rarely; shared with everyone |
| Landline | Home or office phone | Only if a voice-call code is offered |
A second number that you control can receive GitLab's code if it is a real mobile line. Avoid free public numbers: everyone can read them, and GitLab has usually seen them before.
Developer and cloud platforms check phone numbers to keep out abuse of free resources and to protect accounts that can run up bills.
Non-VoIP mobile numbers usually work; numbers from internet calling apps are often refused.
Usually not: most apps allow a number on one account at a time.
Wait a few hours, then request one code.
Often, when you sign in on a new device or change account details. Keep the number, or add email and an authenticator app.
Only for a quick test. Anyone can read the code, and popular apps usually refuse those numbers.
Related: GitLab two-factor codes · GitLab code not received · verification code not received on any app.
Receive SMS online · Non-VoIP numbers · Temporary phone numbers · Free numbers