From c1cb6aacd52d7c4fe2d9e3fe7e55096cd8aeb2fa Mon Sep 17 00:00:00 2001 From: Adam Mills Date: Sat, 16 Sep 2017 17:57:59 -0400 Subject: [PATCH] Update catching up docs to explain force push (#3377) --- source/developers/development_catching_up.markdown | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/source/developers/development_catching_up.markdown b/source/developers/development_catching_up.markdown index 7bfc8064805..88f4b73e078 100644 --- a/source/developers/development_catching_up.markdown +++ b/source/developers/development_catching_up.markdown @@ -24,6 +24,13 @@ If rebase detects conflicts, repeat this process until all changes have been res 4. Continue rebase: `git rebase --continue` 5. Repeat until you've resolved all conflicts +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: + +```bash +# Run this from your feature branch +$ git push origin --force +``` + 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. ```bash