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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-12Lines changed: 3 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -293,25 +293,16 @@ This will automatically update your pull request with the latest code and restar
293
293
294
294
Another reason you might need to update your pull request is to solve conflicts with changes that have been merged into the main branch since you opened your pull request.
295
295
296
-
To do this, you need to “merge upstream main” in your branch:
297
-
298
-
```sh
299
-
git checkout my-new-feature
300
-
git fetch upstream
301
-
git merge upstream/main
302
-
```
303
-
304
-
If there are no conflicts (or they could be fixed automatically), a file with a default commit message will open, and you can simply save and quit this file.
305
-
306
-
In some cases a merge will not work and you will need to rebase instead. To do this run:
296
+
To do this, you need to rebase your branch:
307
297
308
298
```sh
309
299
git checkout my-new-feature
310
300
git fetch upstream
311
301
git rebase upstream/main
312
302
```
313
303
314
-
After the feature branch has been update locally, you can now update your pull request by pushing to the branch on GitHub:
304
+
There may be some merge conficts that need to be resolved. After the feature branch has been update
305
+
locally, you can now update your pull request by pushing to the branch on GitHub:
0 commit comments