Connecting Local & Remote Repositories
📌 Covered in this chapter:
git remote add · origin · HTTPS vs SSH URLs · Managing Remotes
Link your local Git repository to a GitHub remote so you can push and pull changes.
1Connecting Local & Remote Repositories — What You'll Learn
Link your local Git repository to a GitHub remote so you can push and pull changes.
Here's everything this chapter covers, in the order you'll learn it:
- What a 'remote' is in Git
- git remote to view configured remotes
- Adding a remote named origin
- Checking your configured remotes
- HTTPS remote URLs
- SSH remote URLs
- Renaming a remote
- Removing a remote
- Remote-tracking branches
- Why the default remote is conventionally called 'origin'
2Working Example
💻 Example: Connecting Local & Remote Repositories
Bash
git remote add origin https://github.com/username/my-project.git
git remote -v3Best Practices & Common Pitfalls
💡 Key things to remember:
- 'origin' is just a convention/nickname for your primary remote — you could name it anything, but almost every team sticks with 'origin' for consistency.
❓ Frequently Asked Questions (FAQ)
Q What's the most important thing to understand about connecting local & remote repositories?
Focus on: git remote add · origin · HTTPS vs SSH URLs · Managing Remotes. These are the core building blocks this chapter's examples are built around, and they show up repeatedly in later chapters of this course.
Q Is connecting local & remote repositories something I'll use often in real projects?
Yes — every concept in this chapter reflects a real, everyday part of professional Git and GitHub workflows, not just a theoretical exercise.