Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit d97272a

Browse files
authoredAug 3, 2016
GitUsage: recommend rebase rather than merge
1 parent 97faf2f commit d97272a

File tree

1 file changed

+26
-4
lines changed

1 file changed

+26
-4
lines changed
 

‎wiki/GitUsage.md

Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -342,10 +342,32 @@ delete your now redundant bug fix branch on GitHub. Branches can be
342342
deleted by selecting 'edit' and then 'delete repository' from the bottom
343343
of the edit page.
344344

345-
It is mandatory to merge with the current trunk of Biopython (i.e. the
346-
official repository's master branch), or better yet rebase to the
347-
current trunk, before submitting your changes to avoid excess work on
348-
the receiving side.
345+
If other things have happened since you began your work, it may require
346+
merging when applied to the official repository's master branch. In this
347+
case we might ask you to help by rebasing your work:
348+
349+
``` bash
350+
git fetch upstream
351+
git checkout demo-branch
352+
git rebase upstream/master
353+
```
354+
355+
Hopefully the only changes between your branch and the official repository's
356+
master branch are trivial and git will handle everything automatically.
357+
If not, you would have to deal with the clashes manually. If this works,
358+
you can update the pull request by replacing the existing (pre-rebase)
359+
branch:
360+
361+
``` bash
362+
git push origin demo-branch --force
363+
```
364+
365+
If however the rebase does not go smoothly, give up with the following command
366+
(and hopefully the Biopython developers can sort out the rebase or merge for you):
367+
368+
``` bash
369+
git rebase --abort
370+
```
349371

350372
Evaluating changes
351373
------------------

0 commit comments

Comments
 (0)
Please sign in to comment.