GitHub and Remote Repositories: Your Code in the Cloud

Why Do We Need Remote Repositories?

• Local repository — only on your computer
• Remote repository — cloud storage for the team
• Everyone can view and make changes in one place
• Real-time internet synchronization

Imagine you're working on a project alone — a local Git repository is sufficient. But as soon as a team gets involved, you need a shared space. A remote repository becomes the central code storage accessible to every team member. It's similar to Google Docs, where all edits sync in real time. You can see your colleagues' changes, discuss code through pull requests, and work on different features in parallel. Without a remote repository, team development would become chaotic, with endless file versions being emailed back and forth.

How Local and Remote Repositories Connect

• Origin — default name for the remote repository
• Push — send changes to the server
• Pull — retrieve changes from the server
• Each repository is independent and contains complete history

Your local repository communicates with the remote through two key commands: push and pull. The main remote repository is called origin by default. But it's important to understand — this isn't just a simple file copy. Each repository is independent and contains the complete change history. When you make commits locally, they remain only on your machine until you push them. And when colleagues update the code, you retrieve it through pull to synchronize your work.

One Local, Many Remotes

• Multiple remote repositories can be connected
• Origin — your personal fork on GitHub
• Upstream — the original project repository
• Easy to synchronise changes between them

Your project can be connected to multiple remote repositories simultaneously. Let's say 'origin' is your personal fork on GitHub, and 'upstream' is the main project's repository. This setup allows you to make changes to your own copy while easily pulling updates from the original source. This is particularly useful when working with open-source projects where you need to keep your fork up to date. You decide when and which changes to pull from upstream into your origin. Now that we understand the logic of working with remote repositories, it's time to create our own on GitHub — and we'll do that right now.

# Adding a new remote repository
git remote add upstream https://github.com/original/project.git

# Viewing the list of all remote repositories
git remote -v

# Fetching changes from upstream to local branch
git fetch upstream

git checkout main
git merge upstream/main

# Pushing changes to your origin
git push origin main