📝 Git & GitHub

Cloning a Repository in GitHub Desktop 📥

0
Author
04e5cc8b-58ac-4bdc-bdee-661bbb
📅
Published
06.05.2026
⏱️
Reading time
3 min
👁️
Views
42
🌱
Level
Beginner

Want to copy someone else’s (or your own) repository from GitHub? Here’s how to do it through GitHub Desktop!

Three Ways to Clone

Method 1: From your repository list

For your personal repositories:

  1. Open GitHub Desktop
  2. FileClone Repository (or Ctrl+Shift+O)
  3. GitHub.com tab
  4. You’ll see a list of all your repositories
  5. Select the one you want
  6. Choose the Local Path (where to save it)
  7. Clone

✅ In 10-30 seconds the repository will be copied!

Method 2: By URL

For any public or someone else’s repository:

  1. Find the repository on GitHub.com
  2. Click the green Code button
  3. Copy the HTTPS URL (e.g.: https://github.com/username/repo.git)
  4. In GitHub Desktop: FileClone Repository
  5. Go to the URL tab
  6. Paste the URL
  7. Choose Local Path
  8. Clone

Method 3: From the GitHub website (easiest!)

One click:

  1. On the repository page click Code
  2. Choose Open with GitHub Desktop
  3. Confirm in the browser dialog
  4. GitHub Desktop will open automatically
  5. Choose a folder → Clone

🎉 Done!

What to Choose: HTTPS or SSH?

GitHub Desktop uses HTTPS by default — and that’s perfect for beginners!

HTTPS:
- ✅ Works out of the box
- ✅ No setup required
- ✅ Works through firewalls

SSH: (for advanced users)
- Requires generating keys
- Settings on GitHub
- Slightly faster

For now, use HTTPS!

After Cloning

Check the result

In GitHub Desktop you’ll see:

  • History tab — all commits
  • Current Branch — main branch (usually main)
  • Fetch origin — button to check for updates

Open the project

In an editor:
- RepositoryOpen in Visual Studio Code
- Or: Ctrl+Shift+A / Cmd+Shift+A

In file explorer:
- RepositoryShow in Explorer (Windows)
- RepositoryShow in Finder (macOS)
- Or: Ctrl+Shift+F / Cmd+Shift+F

Update the code

If the author updated the repository:

  1. Click Fetch origin
  2. If there are updates, Pull origin will appear
  3. Click Pull to download the updates

Cloning vs Forking

Clone

What: Just a copy for reading/learning

When:
- Want to study the code
- Run the project locally
- Don’t plan to make changes

Problem: Can’t push (upload your changes)

Fork + Clone

What: A copy IN YOUR account + cloning

When:
- Want to make your own changes
- Create a Pull Request
- Build your own version of the project

Steps:

  1. On GitHub.com click Fork (top right)
  2. The repository will be copied to your account
  3. Now clone YOUR copy through GitHub Desktop

✅ Now you can make commits and push!

Working with Forks

After Fork + Clone:

Original:  github.com/author/repo
                ↓ (Fork)
Your fork:  github.com/YOU/repo
                ↓ (Clone)
Your computer:  ~/Projects/repo/

Make changes:

  1. Edit files
  2. Make commits in GitHub Desktop
  3. Push origin — upload to your fork
  4. On GitHub.com create a Pull Request to the original

Sync with the original:

The author updated the repository and you want those changes?

In the terminal:

# Add the original as upstream
git remote add upstream https://github.com/author/repo.git

# Download updates
git fetch upstream

# Merge into your branch
git merge upstream/main

Or on GitHub.com:

  1. Open your fork
  2. If there are updates, you’ll see: “This branch is X commits behind”
  3. Click Sync forkUpdate branch
  4. In GitHub Desktop: Pull origin

Common Issues

“Authentication failed”

Cause: GitHub Desktop can’t log in.

Fix:
1. FileOptionsAccounts
2. Sign out → Sign in again

“Permission denied”

Cause: Repository is private and you don’t have access.

Fix:
- Ask the owner to add you as a collaborator
- Or fork it (if the author allows)

Cloning takes forever

Cause: Large repository or slow internet.

Fix:
- Wait it out (some projects are > 1GB)
- Check your internet speed
- Try again later

“Repository not found”

Cause: Wrong URL or the repository was deleted.

Fix:
1. Check the URL
2. Make sure the repository exists
3. Verify it’s public (or that you have access)

Best Practices

Organize your folders:

~/Documents/GitHub/
├── my-projects/
├── cloned-for-learning/
└── forks/

After cloning:
1. Read README.md
2. Check for package.json / requirements.txt
3. Install dependencies
4. Run the project following the instructions

Don’t commit to a cloned project you don’t own!
- Fork it
- Create your own branch
- Only then commit + push

Update regularly:
- Click Fetch origin
- Pull if there are changes

Cloning is the first step to studying someone else’s code! Good luck! 📦

Your reaction to the article

💬 Comments (0)

🔐 Sign in to leave a comment
🚪 Login
💭

No comments yet

Be the first to share your opinion about this article!

🔗 Similar

Similar articles

Continue learning with these materials

📝

Git Hosting Platforms: Full Comparison 🏆

GitHub, GitLab, Bitbucket — which one to choose? A complete comparison with up-to-date data.

📅 06.05.2026 👁️ 52
📝

What Is a Git Commit and Why Do You Need It? 📸

A commit is a saved snapshot of your project at a specific point in time...

📅 06.05.2026 👁️ 56
📝

Why Git won over every other version control syst…

Today Git is the de facto standard for version control in software development. But it...

📅 06.05.2026 👁️ 51

Did you like the article?

Subscribe to our updates and receive new articles first. Grow with PyLand!