Learn Sync with Upstream | Collaborating with Upstream

When you contribute to an open source project, you typically work on your own fork of the original repository. However, the original repository—often called "upstream"—continues to evolve as other contributors add new features, fix bugs, or improve documentation. If you do not keep your fork up to date with upstream, your code may quickly become outdated or incompatible, making it difficult to contribute changes or resolve conflicts. Syncing with upstream ensures that your work is based on the latest project state, helps avoid merge conflicts, and demonstrates good collaboration practices in active open source communities.


              12345
            
# Add the original repository as an upstream remote
git remote add upstream https://github.com/ORIGINAL_OWNER/REPO_NAME.git

# Fetch the latest changes from the upstream repository
git fetch upstream


              12
            
# Merge changes from the upstream main branch into your current branch
git merge upstream/main

Everything was clear?

Thanks for your feedback!

Section 2. Chapter 1

Ask AI

Ask anything or try one of the suggested questions to begin our chat

Suggested prompts:

How do I resolve conflicts if they occur during the merge?

Can you explain what each git command does in this process?

What should I do after merging the upstream changes into my branch?

Swipe to show menu


              12345
            
# Add the original repository as an upstream remote
git remote add upstream https://github.com/ORIGINAL_OWNER/REPO_NAME.git

# Fetch the latest changes from the upstream repository
git fetch upstream


              12
            
# Merge changes from the upstream main branch into your current branch
git merge upstream/main

Everything was clear?

Thanks for your feedback!

Section 2. Chapter 1