Cloning Repositories

Quiz

...

Explorer

Git

18 lessons

git18

What is Git?Installing and Setting Up Git Creating a Repository Staging and Committing Viewing Status and History Viewing Changes Branching Merging Branches Resolving Merge Conflicts Working with Remotes Pushing and Pulling Cloning Repositories Stashing Changes Ignoring Files Undoing Changes with Reset Cherry-Picking Commits Rebasing Git Best Practices

~//tutorials/git/git-clone/edit

~ Contribute

Suggest a correction or improvement. The author reviews it before it goes live.

Loading...

Comment0 / 300

en/tutorials/git/12git-clone

# Cloning Repositories

Cloning copies a remote repository to your local machine, including its full history.

## Basic Clone

```bash
git clone https://github.com/user/repo.git
```

Creates a `repo/` directory with all files and Git history.

## What Clone Does

- Downloads all repository data
- Creates a working copy of the latest version
- Sets up `origin` remote pointing to the source
- Checks out the default branch (`main`)

## HTTPS vs SSH

```bash
# HTTPS
git clone https://github.com/user/repo.git

# SSH
git clone git@github.com:user/repo.git
```

SSH requires key setup but avoids entering credentials each time.

## Shallow Clone

```bash
git clone --depth 1 https://github.com/user/repo.git
```

Downloads only the latest commit — faster for large repos or CI pipelines.

## Cloning into a Specific Directory

```bash
git clone https://github.com/user/repo.git my-folder
```

## Best Practices

- Use SSH for frequently accessed repos
- Use `--depth 1` for CI/CD or quick inspection
- Clone into a meaningful directory name
- Verify the repository before cloning (check stars, activity)

## Common Mistakes

- Cloning into a non-empty directory
- Not having Git installed
- Using wrong URLs (typos cause failures)
- Confusing cloning with forking

No changes yet

~ hackweb.dev

↑↓ navigate↵ openesc close