You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
'This pull request and the master branch diverged in a way that cannot'
838
+
' be automatically merged. Please rebase on top of the latest master'
839
+
' branch, and let the reviewer approve again.\n'
840
+
'\n'
841
+
'<details><summary>How do I rebase?</summary>\n\n'
842
+
'Assuming `self` is your fork and `upstream` is this repository,'
843
+
' you can resolve the conflict following these steps:\n\n'
844
+
'1. `git checkout {branch}` *(switch to your branch)*\n'
845
+
'2. `git fetch upstream master` *(retrieve the latest master)*\n'
846
+
'3. `git rebase upstream/master -p` *(rebase on top of it)*\n'
847
+
'4. Follow the on-screen instruction to resolve conflicts'
848
+
' (check `git status` if you got lost).\n'
849
+
'5. `git push self {branch} --force-with-lease` *(update this PR)*\n\n'
850
+
'You may also read'
851
+
' [*Git Rebasing to Resolve Conflicts* by Drew Blessing](http://blessing.io/git/git-rebase/open-source/2015/08/23/git-rebasing-to-resolve-conflicts.html)'# noqa
852
+
' for a short tutorial.\n\n'
853
+
'Please avoid the ["**Resolve conflicts**" button](https://help.github.com/articles/resolving-a-merge-conflict-on-github/) on GitHub.'#noqa
854
+
' It uses `git merge` instead of `git rebase` which makes the PR commit'
855
+
' history more difficult to read.\n\n'
856
+
'Sometimes step 4 will complete without asking for resolution. This is'
857
+
' usually due to difference between how `Cargo.lock` conflict is'
858
+
' handled during merge and rebase. This is normal, and you should still'
0 commit comments