From ITSwiki
Jump to: navigation, search

To use git for your own and team projects, DTU Compute is providing a GitLab instance with all the benefits it offers. Primarily a place for your repositories, other features are or will become available.

Login with your DTU credentials here:

Add your public keys

To access your private repositories, add your public SSH-key to your GitLab account.
If you don't have a SSH-key, on Linux/MacOS you can use this command in your favourite shell:


Windows 10 has a native SSH client; in PowerShell create a key pair with:


Press Enter 3 times to create a password-less key pair, located in:


The file is your public key that you can share with other systems, including DTU Compute's GitLab.

To add your public key in GitLab, follow these steps after login:

1) In the top-right corner click your user icon
2) Click Settings and on the left-hand panel click SSH Keys
3) Follow the instructions from here

Give access to other users

To share a repository with other users, the user you want to add has to login to GitLab first. Then you can find and add them as a member of your project.

1) Select your project you want to share
2) In the left-hand panel select Settings -> Members
3) Under Select members to invite search for the username

Instructions for collaboration with user from outside DTU

Users can get access to Gitlab service at DTU Compute only if they have a DTU account. Therefore, if you’d try giving access to an external person through your Gitlab project/group settings, it will not work.

1) Create a guest account for the external person by logging in to with your DTU user and password.
2) After login in, you should see the options as in the figure below. Choose Create user.


3) You should see the form below appearing in the next screen. The username must consist of 8-9 symbols (only letters and digits are allowed). It is important to enable access to DTU Wireless system for Gitlab to be able to discover the new user.


4) After clicking Create user button, you should see the green success message and the information about the user appearing below the search box. You can edit, delete, and change the password for users. Note, that guest users are not able to change credentials themselves and you must do it for them.
5) After certain amount of time (around 1-2 hours), notify the owners of the guest accounts that they should be able to sign in to Gitlab with their new credentials at the Gitlab logon page shown below. The credentials can be sent by email while changing user’s password.


6) You should now be able to share your group/project with your guest users by going to Members setting and clicking the blue Invite members button. The search box will appear where you can search guest users by their usernames in the usual way.

Project Visibility & License

New repositories are per default set to be private which means that only you, and members that you allow, are able to see and work with the repository. This can be changed to either internal ( members) or public (visible to the whole internet). To change the visibility of a repository:

1) Select Settings -> General
2) Expand Visibility, project features, permissions and change Project visibility

NOTE: Please be aware that public repositories can be found in the /public access directory ( If you have projects here that are not meant to be public, change the visibilty of your repository!

If you do want your project to be public, we ask that you add a license. This can be done easily by clicking the Add license link beneath the project name in your project homepage.

Mirroring repositories

It may make sense to mirror a repository to/from an external source such as Github. For instructions read:

Migrating from Gitolite to GitLab

Our Gitolite server ( is considered deprecated, and everyone with active repositories there are encouraged to migrate. This can be done from a local PC with a cloned repo.

Migrating a repo requires a bit of manual work, but not much. What it basically comes down to, is moving the origin from Gitolite to GitLab. Here are the steps described as simple as possible:

  • Make sure your locally cloned repo - incl. all branches, tags, etc. - is up to date with origin
  • Create a new repository on GitLab using the same name as the repo you want to move
  • Add a new remote using the URL from GitLab, and push everything to this remote
  • Remove all references to the old remote (Gitolite)
  • Rename the new remote to origin
  • In GitLab add the users you want to share the project with.
  • Users may want to clone the repo anew rather than change origin manually.

Steps described

As is shown above, it is pretty straight forward to move a repository, but as always the details are important. Here the steps will be described a bit more together with the commands to use.

First make sure that your local repository clone is up to date with origin (the gitolite server), and make sure that you checkout all remote branches locally.

git fetch origin
git branch -a
git checkout -b feature1 origin/feature1

Create the new replacement repository at and copy the SSH clone URL - eg. - to add a new remote in your local repo, and push all branches to this new remote, here called "new-origin".

git remote add new-origin
git push --all new-origin
git push --tags new-origin # if you use tags

Delete the reference to the old origin and make the new remote the origin.

git remote rm origin
git remote rename new-origin origin

Your repository is now migrated to GitLab.

More to come