Quick overview

This short git tutorial shows how to clone a GitLab repository to your local machine with as little drama as possible. You will learn how to find the repository URL on GitLab pick the right access method run the git clone command and verify the local copy. This is essential for version control and basic devops work when you want a working copy of remote repositories.

Locate the repository URL

Open the project page on GitLab and find the Clone menu. Copy the URL shown for the access method you want. Do not reinvent the wheel by typing the URL by hand unless you enjoy debugging small tragedies.

Which access method should you pick

• SSH is best if you plan to push and pull often. Add an SSH key to your GitLab profile and use an SSH agent locally to stop typing your password every minute.
• HTTPS is simpler for one off clones or quick checks. If your account requires stronger auth you will use your username and a personal access token rather than your account password.

Run the clone command

Open a terminal in the folder where you want the repository to live and run the basic clone command shown below. Replace REPO_URL with the URL you copied from GitLab.

git clone REPO_URL

If authentication fails read the error message and follow its hints. Common fixes include adding your SSH key to GitLab starting your SSH agent or creating a personal access token for HTTPS access. Yes it is annoying but it only needs to be done once.

Verify the cloned repository

Change into the new folder and confirm the contents and remote settings. Typical checks are listed below.

cd repo_name
ls
git status
git remote -v

If git status looks sane and git remote -v shows your GitLab remote you are done and can start working locally. If branches look weird run git fetch and inspect branch names.

Troubleshooting and tips

• Tip Prefer SSH for regular work with pushes and pulls. It reduces password typing and looks marginally more professional.
• If your SSH key is not recognized run your SSH agent and add the key with ssh-add. Then upload the public key to GitLab.
• For HTTPS cloning use a personal access token if two factor is enabled or passwords are rejected.
• Use git remote -v and git branch to confirm remotes and branches. These commands save time and embarrassment.

That covers finding the repository URL choosing SSH or HTTPS running git clone and checking the local copy. You now have the remote repository on your machine and permission to be slightly proud of yourself.