When we refer to GitLab in our courses, we always mean the faculty instance available at https://gitlab.mff.cuni.cz.

Use your CAS credentials to log in, i.e., the same credentials you use to access SIS. Use the username derived from your first and family name (such as doejohn, in lower case letters) instead of the numerical identifier.

Your first login will activate your GitLab account. Without that, it is impossible to provide you with access to your course repositories.

For some courses this might mean that you will not be able to submit assignments required to pass the course (please, consult the course requirements for further details).

How do I sign in?

If you cannot log in, try changing your CAS password (even to a temporary one — you can change it back to your original password later) to trigger password synchronization. Note that you may need to wait up to one full day before the effect of the synchronization becomes visible.

For some new accounts (typically Erasmus students and, in certain situations, also BINF students) it is necessary to wait for an extra synchronization round that is performed at midnight every day. Try to change the password the next morning and try logging in to GitLab few hours after that.

Note also that you need to have an account with so-called verified password (this typically applies to Erasmus students only). You need to visit one of these offices to verify your account.

If you are from a different faculty than MFF (except BINF students from the Faculty of Science), please, contact the course teachers directly as your account could not be automatically synchronized.

Also note that for some accounts, projects were enabled only after you filled-in your e-mail address in your profile.

If your account still does not work, please, do not hesitate to contact your course teacher(s) as soon as possible.

Where is my project?

The easiest way is to look at the Member tab at the home page of GitLab.

If you just signed-in for the first time, no projects will be there. Your teacher can create them for you only after you sign in, i.e. after your account is activated.

Pro tip: clicking on the Star in your project will put it under the Starred tab that can be configured to be your default page – thus you will see only the projects you need at the moment.

My submission was not graded!

Grading of the assignments is specific for each course so, please, always consult rules and requirements of your course.

As a general rule, you will be usually asked to work with a specific repository private for you. Do not fork that repository (unless explicitly asked to) because your teacher will not have access to the fork and thus will not be able to view your solution.

For some courses the submission is graded semi-automatically and pushing your solution under a different filename is virtually the same as not providing it at all. Git and GitLab are case-sensitive on filenames, hence solution.md and SOLUTION.md are different files (another common issue is some extra space, such as SOLUTION␣.md).

Working with Git and GitLab

Except for the Introduction to Linux (NSWI177) course, we expect you are able to work with Git and GitLab (we rarely require any advanced knowledge but knowing the basic Git commands of clone, pull, push, status, log, add and commit is a must).

If you are on an some kind of an exchange program or you simply need a refresher, than following links might help you get started (however, any decent tutorial for Git will be fine too).

Note: if you are enrolled to NSWI177 Introduction to Linux, then we will go through the topics above in the course. Please, only make sure you can login to MFF GitLab.