One-time setup

Git and GitHub (one-time setup)

If you are a bioconda team member (having been added by posting in issue #1), then you have push access to the repo. In this case you can clone the bioconda-recipes repo:

Decide whether you’ll work on a clone or a fork.

Choose a clone if:

  • You are a bioconda team member (post on issue #1 if you’d like to join). Team members have write access to branches other than the master branch.
  • You want to have other team members make changes directly to your branch

Choose a fork if:

  • you are not yet a member of the bioconda team
  • you expect to do lots of testing or lots of troubleshooting. This will allow you to use your own quota on travis-ci, so your builds will likely happen faster and you won’t be consuming limited bioconda quota.

Using a clone

Clone the main repo:

git clone

You can now move on to installing requirements (next section).

Using a fork

If you do not yet have push access, then create a fork of bioconda-recipes on GitHub. Then clone it locally:

git clone<USERNAME>/bioconda-recipes.git

Then add the main bioconda-recipes repo as an upstream remote to more easily update your branch with the upstream master branch:

git remote add upstream

Install Docker (optional)

Installing Docker is optional, but allows you to simulate most closely the Travis-CI tests.

Request to be added to the bioconda team (optional)

While not required, you can be added to the bioconda by posting in Issue #1. Members of the bioconda team can merge their own recipes once tests pass, though we ask that first-time contributions and anything out of the ordinary be reviewed by the @bioconda/core team.