Getting Started

GitLab Pilot Service Retiring July 31, 2023

Access to U-M GitLab will be disabled on July 31, 2023. ITS will be communicating with GitLab users to help them migrate off of the U-M GitLab service to an alternative. Find out more about U-M GitLab retirement.

Access to GitLab will be removed on July 31, 2023. The on-premise GitLab infrastructure will be decommissioned in Fall 2023. See GitLab Retirement Project for more information.

Logging In

Log in to the U-M GitLab service at Click the button labeled U‑M Shibboleth SSO, and proceed through Weblogin using your kerberos (Level-1) credentials. If you don't already have an account, one will be created for you on your first login.

Sensitive Data

The U-M GitLab service is not approved for sensitive, regulated data types. It is up to the U-M individual using the service to ensure these types of data are not inadvertently or otherwise included in a GitLab repository (client or server side). This includes keys, credentials, data files, and other secure data. The following are some helpful links:

This IT Security Liaisons list can be used to determine the name of your unit or department contact.


  • Establish backup and/or archive service as required to meet U-M and unit or department policies
  • Establish policies and a process for software development collaboration and version control
  • The default ITS GitLab runner is a shared resource and is subject to slowdowns during heavy usage. If you need to avoid processing delays, you can run your own GitLab runner that is dedicated just to your group.

Commit Code Frequently with Good Comments

Use Branching

At a minimum, projects should have development and production branches.

Don't Add Large Files to a Git Repository

Store large files somewhere else and have your code retrieve them.

Take Advantage of the Other Collaboration Feature