TruthsSeek
English

Guide Published 2026-10-23 · Updated 2026-10-23

Record a GitLab User ID Before Comparing Renamed Profiles

TruthsSeek publication · Editorial policy

Quick answer · A GitLab username sits in its own namespace, and that namespace changes when the username changes, so a profile link built only on the username can stop resolving. GitLab also exposes a user-ID URL of the form /-/u/ followed by the ID, which stays tied to the account rather than the current handle. Recording the host, that exact URL, the observed username and the date gives you a fixed reference for later comparison.

Run this check now — TraceSeek scans 3,000+ platforms in 20–30s. First scan free.

⬇︎ iOS⬇︎ Android

Why the username alone is a weak reference

A GitLab username is not just a label on a profile page; it defines a namespace. When someone renames their account, the namespace changes with it, so a saved profile link that relies on the old handle may no longer point where you expect.

A GitLab username has its own namespace, which changes when the username changes. Source

That is the practical problem this record solves. If you want to compare a profile before and after a rename, or check whether two profiles are the same account, you need an identifier that does not depend on the current username.

What to write down

Keep one entry per profile you are tracking. Four fields are enough to make the note useful later:

FieldWhat to captureWhy it matters
HostThe GitLab installation the profile lives on, e.g. GitLab.com or a self-hosted instanceUser IDs are only meaningful within one installation
User-ID URLThe exact /-/u/<ID> address for the accountA reference that does not depend on the current username
Observed usernameThe handle shown at the time you lookedLets you match the record to what you saw
DateThe day you recorded itTells you which observation the note describes

Record the URL exactly as it appears rather than retyping it from memory. A single mistyped character turns a useful reference into a dead link, and you may not notice until months later when you need it.

Getting the user-ID URL from a profile

GitLab profiles can be reached through a user-ID path rather than only through the username path.

GitLab profiles can be opened through a user-ID URL in the form /-/u/ followed by the ID rather than only through the username path. Source

The ID itself can be read from the profile page. On a profile, the Actions area includes a Copy user ID option.

From a profile page, Actions includes Copy user ID. Source

A workable order is:

  1. Open the profile while you can still see it, and note the host in the address bar.
  2. Copy the user ID from the profile’s Actions area.
  3. Build or save the /-/u/<ID> address for that host, and check that it opens the same profile.
  4. Write down the username you observed and today’s date next to it.
  5. Store the four fields together, so the URL is never separated from the host and date it belongs to.

Step 3 is the one worth slowing down for. If the user-ID URL does not open the profile you were looking at, the record is wrong, and it is better to find that out now than after the username has changed.

Keep installations separate

GitLab.com is one installation, but GitLab software also runs on many other hosts. A user ID is an identifier within a single installation, so the same number can belong to a different account somewhere else. A record that says only “GitLab, ID 12345” is ambiguous; a record that says which host the ID came from is not.

Treat each host as its own set of records. Do not merge entries from two installations into one list, and do not assume a URL pattern copied from one host will resolve on another.

What the record can and cannot tell you

QuestionWhat the record supportsWhat it does not
Is this the same account I looked at before?A comparison between the stored user-ID URL and the current oneProof that a real person is behind either profile
Did the username change?A visible difference between the stored username and the current oneWhy it changed, or who changed it
Is this profile still active?Whether the URL still resolves when you checkAny conclusion about activity level from the profile alone

A profile match is a lead, not proof of ownership. Two profiles that share a handle, a photo or a short biography do not thereby belong to the same person, and a matching user-ID URL tells you the account is the same account, not that you know who operates it.

When the comparison is inconclusive

Several outcomes are normal, and none of them should be read as a verdict about a person:

If you cannot resolve the ambiguity, say so in your notes. An honest “unresolved” entry is more useful later than a confident one built on a guess.

Where this fits in a wider check

This record is a narrow, durable reference for one platform. If your actual task is broader — working out which accounts across different services might belong to the same person — a username lookup across many platforms is the natural next step, and the guide on finding social media accounts by username covers that task. Keep the GitLab record separate from that broader picture: it documents an account reference, while the wider search produces candidates that still need checking.

If you use a lookup tool for that broader step, treat its output the same way — as leads to verify, not conclusions. TraceSeek, the app covered by this publication, states that it searches 3,000+ platforms and that a first scan is free and takes 20-30 seconds; those are product statements, not independent measurements, and a public match still does not establish who owns an account.

A short checklist

Frequently asked questions

Why not just save the profile link with the username in it?

Because the username can change. A GitLab username has its own namespace, and that namespace changes when the username changes, so a username-based link may stop pointing at the account. A user-ID URL gives you a reference that does not depend on the current handle.

Where do I find the user ID on a GitLab profile?

From a profile page, the Actions area includes a Copy user ID option. You can then use that ID in a /-/u/ URL to open the profile by ID rather than by username.

Does the same user ID mean the same account on any GitLab site?

No. A user ID identifies an account within one GitLab installation. GitLab.com and a self-hosted GitLab instance are separate installations, so always record which host an ID came from.

Does a matching profile prove who the person is?

No. A record can help you compare whether an account appears continuous over time, but a username, photo or biography match is a lead, not proof of a real person's identity.

Keep reading

Ready to look someone up?

See what a username reveals

According to its product information, TraceSeek searches 3,000+ platforms in 20–30 seconds and surfaces publicly accessible profiles matching a username. The first scan is free. Possible matches need manual review. No registration or sign-in is needed for the first scan.

⬇︎ Download for iOS⬇︎ Get it on Android

Works on iPhone & Android · 20–30 second scan · 3,000+ platforms

⬇︎ App Store ⬇︎ Google Play