Skip to content

Commit c1cb6aa

Browse files
emlovefabaff
authored andcommitted
Update catching up docs to explain force push (home-assistant#3377)
1 parent 857de4a commit c1cb6aa

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

source/developers/development_catching_up.markdown

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,13 @@ If rebase detects conflicts, repeat this process until all changes have been res
2424
4. Continue rebase: `git rebase --continue`
2525
5. Repeat until you've resolved all conflicts
2626

27+
After rebasing your branch, you will have rewritten history relative to your GitHub fork's branch. When you go to push you will see an error that your history has diverged from the original branch. In order to get your GitHub fork up-to-date with your local branch, you will need to force push, using the following command:
28+
29+
```bash
30+
# Run this from your feature branch
31+
$ git push origin --force
32+
```
33+
2734
Other workflows are covered in detail in the [Github documentation](https://help.github.com/articles/fork-a-repo/). Add an additional `remote` after you clone your fork.
2835

2936
```bash

0 commit comments

Comments
 (0)