Skip to content

Commit 0a9d06a

Browse files
committed
Merge remote-tracking branch 'origin/master' into develop
2 parents 34bc896 + f667821 commit 0a9d06a

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/newbs_git_resynchronize_a_branch.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -51,21 +51,21 @@ git remote set-url origin https://github.com/<your_username>/qmk_firmware.git
5151
Now that you have both remotes configured, you need to update the references for the upstream repository, which is QMK's, by running:
5252

5353
```
54-
git fetch upstream
54+
git fetch --recurse-submodules upstream
5555
```
5656

5757
At this point, resynchronize your branch to QMK's by running:
5858

5959
```
60-
git reset --hard upstream/master
60+
git reset --recurse-submodules --hard upstream/master
6161
```
6262

6363
These steps will update the repository on your computer, but your GitHub fork will still be out of sync. To resynchronize your fork on GitHub, you need to push to your fork, instructing Git to override any remote changes that are not reflected in your local repository. To do this, run:
6464

6565
```
66-
git push --force-with-lease
66+
git push --recurse-submodules=on-demand --force-with-lease
6767
```
6868

69-
!> **DO NOT** run `git push --force-with-lease` on a fork to which other users post commits. This will erase their commits.
69+
!> **DO NOT** run `git push --recurse-submodules=on-demand --force-with-lease` on a fork to which other users post commits. This will erase their commits.
7070

7171
Now your GitHub fork, your local files, and QMK's repository are all the same. From here you can make further needed changes ([use a branch!](newbs_git_using_your_master_branch.md#making-changes)) and post them as normal.

0 commit comments

Comments
 (0)