CAUTION: Caution:
It is currently not possible to change your username if it contains a
project with Container Registry tags,
because the project cannot be moved.

TIP: Tip:
If you want to retain ownership over the original namespace and
protect the URL redirects, then instead of changing a group's path or renaming a
username, you can create a new group and transfer projects to it.
Alternatively, you can follow this detailed procedure from the GitLab Team Handbook
which also covers the case where you have projects hosted with
GitLab Pages.

Current status

Introduced in GitLab 11.2.

You can provide a custom status message for your user profile along with an emoji that describes it.
This may be helpful when you are out of office or otherwise not available.
Other users can then take your status into consideration when responding to your issues or assigning work to you.
Please be aware that your status is publicly visible even if your profile is private.

To set your current status:

Open the user menu in the top-right corner of the navigation bar.

Hit Set status, or Edit status if you have already set a status.

Set the emoji and/or status message to your liking.

Hit Set status. Alternatively, you can also hit Remove status to remove your user status entirely.

Private commit email

GitLab provides the user with an automatically generated private commit email option,
which allows the user to not make their email information public.

To enable this option:

Open the user menu in the top-right corner of the navigation bar.

Hit Commit email selection box.

Select Use a private email option.

Hit Update profile settings.

Once this option is enabled, every Git-related action will be performed using the private commit email.

In order to stay fully annonymous, you can also copy this private commit email
and configure it on your local machine using the following command:

git config --global user.email "YOUR_PRIVATE_COMMIT_EMAIL"

Troubleshooting

Why do I keep getting signed out?

When signing in to the main GitLab application, a _gitlab_session cookie is
set. _gitlab_session is cleared client-side when you close your browser
and expires after "Application settings -> Session duration (minutes)"/session_expire_delay
(defaults to 10080 minutes = 7 days).

When signing in to the main GitLab application, you can also check the
"Remember me" option which sets the remember_user_token
cookie (via devise).
remember_user_token expires after
config/initializers/devise.rb -> config.remember_for (defaults to 2 weeks).

When the _gitlab_session expires or isn't available, GitLab uses the remember_user_token
to get you a new _gitlab_session and keep you signed in through browser restarts.

After your remember_user_token expires and your _gitlab_session is cleared/expired,
you will be asked to sign in again to verify your identity (which is for security reasons).