Skip to content

Instantly share code, notes, and snippets.

@kayagultekin
Last active August 25, 2022 16:20
Show Gist options
  • Star 3 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save kayagultekin/557975964ae26b99b46be3082ee828cf to your computer and use it in GitHub Desktop.
Save kayagultekin/557975964ae26b99b46be3082ee828cf to your computer and use it in GitHub Desktop.
Sync a forked repository with the remote source

Configuring a remote for a fork

source: https://help.github.com/articles/configuring-a-remote-for-a-fork/

You must configure a remote that points to the upstream repository in Git to sync changes you make in a fork with the original repository. This also allows you to sync changes made in the original repository with the fork.

  1. Open Git Bash.

  2. List the current configured remote repository for your fork.

    git remote -v

    origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (fetch)
    origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (push)

  3. Specify a new remote upstream repository that will be synced with the fork.

    git remote add upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git

  4. Verify the new upstream repository you've specified for your fork.

    git remote -v

    origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (fetch)
    origin https://github.com/YOUR_USERNAME/YOUR_FORK.git (push)
    upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (fetch)
    upstream https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git (push)

Syncing a fork

source: https://help.github.com/articles/syncing-a-fork/

Sync a fork of a repository to keep it up-to-date with the upstream repository.

Before you can sync your fork with an upstream repository, you must configure a remote that points to the upstream repository in Git.

  1. Open Git Bash.

  2. Change the current working directory to your local project.

  3. Fetch the branches and their respective commits from the upstream repository. Commits to master will be stored in a local branch, upstream/master.

  4. Check out your fork's local master branch.

    git checkout master

    Switched to branch 'master'

  5. Merge the changes from upstream/master into your local master branch. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.

    git merge upstream/master

    Updating a422352..5fdff0f
    Fast-forward
    README | 9 -------
    README.md | 7 ++++++
    2 files changed, 7 insertions(+), 9 deletions(-)
    delete mode 100644 README
    create mode 100644 README.md

  6. If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":

    git merge upstream/master

    Updating 34e91da..16c56ad
    Fast-forward
    README.md | 5 +++--
    1 file changed, 3 insertions(+), 2 deletions(-)

Pushing to a remote

source: https://help.github.com/articles/pushing-to-a-remote/

Use git push to push commits made on your local branch to a remote repository.

The git push command takes two arguments:

A remote name, for example, `origin`
A branch name, for example, `master`

For example:

git push <REMOTENAME> <BRANCHNAME>

As an example, you usually run git push origin master to push your local changes to your online repository.

What about Syncing Tags?

What worked for me was:

  1. Get all the remote tags to local git:

    git fetch --tags --all

  2. Push all local tags to my fork:

    git push --tags

@chandrareddyp
Copy link

What does "Open Git Bash."?

@kayagultekin
Copy link
Author

What does "Open Git Bash."?

It is a command-line application that is installed with git on windows systems. On which you can execute git commands...
Please refer to this link for a brief...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment