Bevor Du einen Fork mit dem ihm vorgelagerten Repository synchronisieren kannst, musst Du in Git ein Remote-Repository konfigurieren, das auf das vorgelagerte Repository verweist.
- Öffne TerminalTerminalGit Bash.
- Wechsle Dein aktuelles Arbeitsverzeichnis in das lokale Projekt.
- Rufe die Branches und die jeweiligen Commits aus dem vorgelagerten Repository ab. Commits to
BRANCHNAME
will be stored in the local branchupstream/BRANCHNAME
.$ git fetch upstream > remote: Counting objects: 75, done. > remote: Compressing objects: 100% (53/53), done. > remote: Total 62 (delta 27), reused 44 (delta 9) > Unpacking objects: 100% (62/62), done. > From https://hostname/ORIGINAL_OWNER/ORIGINAL_REPOSITORY > * [new branch] main -> upstream/main
- Check out your fork's local default branch - in this case, we use
main
.$ git checkout main > Switched to branch 'main'
- Merge the changes from the upstream default branch - in this case,
upstream/main
- into your local default branch. This brings your fork's default branch into sync with the upstream repository, without losing your local changes.
If your local branch didn't have any unique commits, Git will instead perform a "fast-forward":$ git merge upstream/main > 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
$ git merge upstream/main > Updating 34e91da..16c56ad > Fast-forward > README.md | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-)
Tipp: Das Synchronisieren Deiner Fork wird nur die lokale Kopie Deines Repositorys aktualisiert. To update your fork on your GitHub Enterprise Server instance, you must push your changes.