100% private · no tracking · works offline100% client-side/no data leaves your browser/no accounts/works offline
Master the fundamental operations for working with remote repositories in Git
Master essential Git remote operations: clone, fetch, pull, and push commands.
Cloning creates a copy of a remote repository on your local machine, including all its branches and history. It's typically your first step when working with an existing project.
When you clone a repository, Git automatically sets up the remote as 'origin' and creates a local branch for each remote branch, typically starting with 'main' or 'master'.
Fetching downloads new changes from the remote repository but doesn't integrate them into your working files. This is a safe way to review changes before merging.
Pulling fetches changes from a remote repository AND merges them into your current branch. It's essentially a combination of fetch and merge.
- Downloads changes only
- Doesn't modify working branch
- Safer option for review
- Downloads and merges changes
- Updates working branch
- Faster for integration
Pushing uploads your local changes to a remote repository, making them available to others. It's how you share your work with the team.
Using --force can overwrite remote history. Only use it when absolutely necessary and you understand the consequences. Consider using --force-with-lease instead.
Here are some common scenarios you'll encounter when working with remotes:
- Working with pull requests
- Code review workflows and best practices