This page explains the end-to-end Git, GitLab@UTwente, and GitHub Desktop workflow.

<aside> <img src="/icons/git_blue.svg" alt="/icons/git_blue.svg" width="40px" />

To submit your work via GitLab you must go to **gitlab.utwente.nl/getxr2026** and click Request Access!

</aside>

Git, GitLab, GitHub …

If you are new to version control, here is how the different pieces connect:

• Git: The version control engine tracking file history and changes on your computer.
• GitLab (gitlab.utwente.nl): The university's remote cloud server storing your repository.
• GitHub Desktop: The visual desktop app on your computer that lets you manage your Git repository without typing terminal commands.

Fork, Clone, Commit, Push:

• Fork creates a personal copy of the repository in the cloud (on GitLab) under your account.
• Clone downloads a copy of that cloud repository onto your local computer.
• Commit creates a local checkpoint on your laptop – it’s not uploaded yet.
• Push uploads your commits to the GitLab server.

flowchart LR
    A["FORK on GitLab"] --> B["CLONE via GitHub Desktop"]
    B --> C["Make changes"]
    C --> D["COMMIT locally"]
    D --> E["PUSH to GitLab"]

Why Use It?

• Safety Net & Revert: Broken a script or messed up a Unity scene? Instead of panicking or keeping Project_final_v3_FINAL.zip, you can inspect what broke and revert to your last working checkpoint.
• Multi-Machine Sync & Cloud Backup: Work on a desktop at home, push your changes, and pull them down on your laptop in the lab. If your laptop crashes, your full history is safely backed up on GitLab.
• Effortless Submission: No huge .zip files to upload on Canvas. Pushing to GitLab gives teaching staff direct access to pull and grade your project.

One-Time Setup: Authentication & Tools

Course Group Membership (getxr2026)

To be able to share your private assignment forks with the teaching staff, your GitLab account must be connected to the course group. Visit gitlab.utwente.nl/getxr2026 and click the Request Access button.