[Biopython-dev] biopython on github

[Giovanni Marco Dall'Olio]

On Fri, Mar 20, 2009 at 9:44 PM, Peter <biopython at maubp.freeserve.co.uk> wrote:

> If I understand correctly, a potential contributor does this:
> 1. Fork Biopython trunk at GitHub, which will give you your own
> public repository (aka a "fork" in github's terminology), called
> by default contributorname/biopython, containing initially a
> single master branch, e.g.
> http://github.com/peterjc/biopython/tree/master
> 2. Using the git command line tool, create a branch within your
> repository to work on a problem, say bug2551, and upload this
> branch to your github account. e.g.
> http://github.com/peterjc/biopython/tree/bug2551 (I presume)
> 3. Work on your code, and commit changes to your bug2551 branch
> and push these up to your github account.
> 4. Once you are happy, submit this bug2551 branch for inclusion in
> Biopython (in the short term via Bugzilla, but if/when we have moved
> to github fully, as a pull request to the main biopython master,
> or if appropriate the master of the mainterainer of that module).
> 5. Once the changes are in the main Biopython, you can delete
> the bug2551 branch (but not the whole "fork" which may contain
> other branches).


Yes, I think this is the procedure.
It is a good idea to create a branch with a bug's name, so more people
can work at the same time on the same fix.





-- 

My blog on bioinformatics (now in English): http://bioinfoblog.it