Gitoryxgit clone is how you download a repository to your local machine. This tutorial explains the different cloning methods, options like depth and branch selection, and how to handle common issues.
You want to work on a project hosted on GitHub or GitLab. You could download the ZIP — but then you'd lose all Git history and collaboration features. The right tool is git clone.
Cloning is how every developer gets a local copy of a remote repository. It downloads the full history, sets up the remote origin automatically, and puts you ready to commit, push, and collaborate immediately.
Common mistakes developers make with this:
git pull (you can't pull what doesn't exist locally)Gitoryx: Gitoryx lets you clone any repository by pasting a URL — it handles HTTPS and SSH automatically and opens the repo in the visual interface as soon as the clone completes.
git clone creates a local copy of a remote repository, including its full history, branches, and tags. It automatically creates a remote called origin pointing back to the source.
On GitHub, GitLab, or Bitbucket, click the 'Code' or 'Clone' button and copy the URL. You'll see two options: HTTPS and SSH.
Use SSH if you've set up SSH keys — you'll never be prompted for a password. Use HTTPS for a quick start without SSH setup.
Run git clone <url> in the terminal. Git creates a new folder with the repository name and downloads everything inside.
# Clone via HTTPS
git clone https://github.com/user/my-project.git
# Clone via SSH
git clone git@github.com:user/my-project.gitBy default, Git names the folder after the repo. Pass a second argument to use a different name.
git clone git@github.com:user/my-project.git frontendBy default, you get the default branch (usually main or master). Use -b to start on a specific branch.
git clone -b develop git@github.com:user/my-project.gitTo clone the exact state of a tagged release — useful for reproducing a specific version or auditing old code:
git clone --branch v2.3.0 git@github.com:user/my-project.gitThe --branch flag accepts both branch names and tag names. The resulting clone checks out that tag directly.
See this workflow in Gitoryx. Paste any HTTPS or SSH URL and clone with one click
Free downloadIf the repository has a very long history and you just need the latest code, --depth 1 clones only the most recent commit. You can also do a partial clone with --filter to skip large binary blobs entirely.
# Shallow clone — only the latest commit
git clone --depth 1 git@github.com:user/large-repo.git
# Partial clone — skip large binary objects (Git 2.22+)
git clone --filter=blob:none git@github.com:user/large-repo.git
# Shallow + specific branch
git clone --depth 1 --branch develop git@github.com:user/large-repo.gitShallow clones lack full history. Commands like git log, git bisect, and git blame will be limited. Don't use --depth 1 if you plan to contribute back.
A bare clone contains only the Git objects with no working directory — used for server hosting or backups. A mirror clone is a bare clone that also copies all refs (branches, tags, notes) and is kept in sync.
# Bare clone (for hosting / server use)
git clone --bare git@github.com:user/my-project.git my-project.git
# Mirror clone (full backup including all refs)
git clone --mirror git@github.com:user/my-project.git my-project.git
# Update a mirror clone later:
cd my-project.git
git remote updateUse --bare when setting up a central Git server. Use --mirror for full automated backups — it replicates every ref exactly.
Git supports three URL formats for cloning. Each has different authentication requirements and use cases.
# HTTPS — easy to start, prompts for credentials or uses credential manager
git clone https://github.com/user/my-project.git
# SSH — requires SSH key setup, no password prompts after that
git clone git@github.com:user/my-project.git
# Git protocol — fast, read-only, used for public open-source repos
git clone git://github.com/user/my-project.git
# Switch an existing clone from HTTPS to SSH:
git remote set-url origin git@github.com:user/my-project.gitFor daily development, SSH is the best choice: set up your key once and never enter a password again. HTTPS is fine for a quick one-off clone.
After cloning, enter the folder and check the remote is set correctly.
cd my-project
git remote -v
# origin git@github.com:user/my-project.git (fetch)
# origin git@github.com:user/my-project.git (push)Git refuses to clone into a folder that already contains files.
Fix: Create a new empty folder first, or let Git create it automatically by not passing a destination path.
Without a credential helper or SSH keys, Git asks for your username and password each time.
Fix: Set up SSH keys and use the SSH clone URL, or configure Git Credential Manager.
If you don't have write access to the repo, you need to fork it first, then clone your fork.
Fix: Fork the project on GitHub/GitLab, then clone your own fork.
Gitoryx — macOS & Windowsgit clone creates a brand new local copy of a remote repository from scratch. git pull updates an existing local repository with new changes from the remote. You clone once; you pull many times.
Forking creates a copy of a repository under your own account on a hosting platform (GitHub, GitLab). Cloning downloads a repository to your local machine. You typically fork first on GitHub, then clone your fork locally.
Yes, as long as you have access. Use SSH keys or HTTPS with your credentials. On GitHub you can also use a personal access token in place of a password.
Yes, all remote branches are fetched, but only the default branch is checked out locally. Use git checkout -b <branch> origin/<branch> to switch to another branch after cloning.
Use git clone -b <branch-name> <url>. This checks out the specified branch, though the other remote branches are still available.
Large repos can be slow because Git downloads the full history of every file. Use --depth 1 for a shallow clone of only the latest commit, or --filter=blob:none for a partial clone that skips large binary objects.
A bare clone (git clone --bare) creates a copy that contains only Git's internal objects with no working directory. Bare repositories are used for hosting and server-side backups — they're what services like GitHub store on their servers.
HTTPS clone URLs (https://github.com/...) use password or token authentication and work anywhere. SSH clone URLs (git@github.com:...) use key-based authentication — faster for daily use once you set up your SSH key, and no password prompts.
Pass the desired folder name as a second argument: git clone <url> my-folder-name. Git will create a folder with that name instead of the repo's default name.
Everything in this tutorial is faster and clearer with a visual Git client. Gitoryx is free, runs natively on macOS and Windows, and built for developers who want to move fast without breaking things.