This includes GitLab Pages at utwente.io and use of the provided CI.
Use of GitLab for most regular development scenarios is allowed. We only ask you to abide by the following:
Fair use: The hosting of repositories and webpages, and the use of the CI runners is offered on a fair use basis. While there are no hard limits, please try to keep the total size of your repositories, individual build artefacts and Docker images reasonable (<1 GB, <100 MB and <500MB respectively).
Educational use: Only educational use—as defined in the Gitlab Education Terms—is allowed. This means that the GitLab can only be used in relation to learning, teaching and/or training.
No abuse: This is a rule which describes many actions. Always try to use your common sense. Every admin has the right to take actions as they see fit. These actions are not open for debate.
Personal use of Gitlab is allowed. Hosting your personal projects (learning, teaching or training projects) or building your personal (portfolio) website, for example.
We may update these rules whenever this is required for offering the service.
Accounts will be deleted one year after the associated accounts is blocked by the University. This usually happens after graduation or termination. During this year it is possible to contact us at firstname.lastname@example.org to request a copy of your data.
Students that start working at the University after graduation and want to keep their current GitLab account can contact us at email@example.com: we will ensure that your employee credentials are associated with your GitLab account.
Avoid storing binary files in Git. For Office-like files this means storing
.docx. Use Git LFS if you absolutely have to store binary files.
Use our GitLab bot for notifications.