Skip to content

Commit f56e0b7

Browse files
authored
Merge pull request #98 from sanders41/contributing
Updating rebase info
2 parents 27a7f98 + 9be469d commit f56e0b7

File tree

1 file changed

+3
-12
lines changed

1 file changed

+3
-12
lines changed

CONTRIBUTING.md

Lines changed: 3 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -293,25 +293,16 @@ This will automatically update your pull request with the latest code and restar
293293

294294
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.
295295

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:
307297

308298
```sh
309299
git checkout my-new-feature
310300
git fetch upstream
311301
git rebase upstream/main
312302
```
313303

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:
315306

316307
```sh
317308
git push origin my-new-feature

0 commit comments

Comments
 (0)