So, you want to add a new pipeline to nf-core - brilliant! Before you start typing, check that you're happy with the following points:
- You're familiar with nf-core and nextflow (see our introduction docs).
- You're used to working with
gitand GitHub (see a nice tutorial here)
- The workflow you're thinking of meets the nf-core guidelines.
The main steps involved in adding a new nf-core pipeline covered below are:
- Joining the community
- Creating a pipeline
- Adding test data
- Adding to the nf-core organisation
- Making your first release
- Updates and new releases
At its heart, nf-core is a community - to add a pipeline you need to be part of that community! Please request to join the nf-core GitHub organisation) and introduce yourself on Slack or the mailing list.
It's good to introduce your idea early on so that it can be discussed before you spend lots of time coding.
You'll start by making a new pipeline locally and working with it on your own GitHub account. Only when it's ready do we move ito the nf-core GitHub organisation.
It's highly recommended to use the nf-core template.
The guidelines for nf-core pipelines are pretty strict, but if you start your pipeline by using the
nf-core template (
nf-core create - see the docs)
then your life will be much easier.
This tool does lots of things for you: it gives you the correct file structure and boiler plate code
and also sets up the required
git infrastructure for you to keep your pipeline in sync in the future.
Even if you already have a working pipeline, it may be easier in the long run to use this this template and copy over your code in the relevant places.
If you really don't want to use the template it should possible to work without it. Please see the manual synchronisation documentation.
Note that workflow names should be all lower-case and contain no punctuation. This is to allow consistent names between platforms (eg. GitHub + Docker Hub).
Create a repository on GitHub for your new pipeline under your personal account.
Do this by going to the GitHub website and clicking + then New Repository.
Make sure not to initialise it with
README file - you just want an empty repository.
Once created, copy the URL and add this as a remote to your local git repository and push your code:
## Add a remote called 'origin' - this is the default name for a primary remote git remote add origin https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.git ## Commit any new code changes since you ran the template git add . git commit -m "Starting to build my pipeline" ## Push to GitHub git push
The nf-core pipelines use two additional services that link to GitHub: Travis and Dockerhub. Using these enables automated testing (Travis) and automatic Docker image builds (Docker Hub).
Just like with GitHub, you can run these on your personal fork for testing purposes. Once you've merged your pipeline in to the nf-core organisation, we will also set them up there, but that happens later.
To enable Travis, go to travis-ci.com and log in with your
GitHub credentials. Add a new GitHub repository and select your new pipeline.
The repository should already contain the required
.travis.yml file, so the next
time you push a commit the tests will be automatically triggered.
The process for Docker Hub is similar, though a little more fiddly. Docker has a number of different docker websites (docker hub, docker cloud, docker swarm etc.), but they seem to be moving towards consolidating on just Docker Hub. So it's best to use that.
- Go to hub.docker.com and create an account
- Create a new repository for your workflow
- Set your repository to be automatically built from a GitHub repository and link it to your workflow
- Configure the repo to automatically build whenever you push a new commit to your GitHub repo
Whilst developing your pipeline on your local fork you will need to create automated builds for two docker images
with source set to
master - one with the
dev tag and the other with the
The former will be required for Travis and the latter will be pulled when executing the pipeline locally.
Note: The template assumes that your Docker image is hosted on the nf-core Docker Hub organisation.
To make the pipeline work with your testing image, switch out
nfcore/<PIPELINE_NAME> for your address
username/<PIPELINE_NAME>). You'll find this in the
container variable in
docker commands in
These will need to be changed back to the defaults before you fork the pipeline to
Ok, now you're all set with your own personal nf-core pipeline!
You can now start writing code for real.
Remember to keep running the
nf-core lint command (see docs)
to make sure that your workflow passes all of the nf-core tests.
The automated tests on Travis also run this so you should get an email if something breaks.
Whilst the linting tests are good, they're not sufficient by themselves. It's also good to get Travis to actually run your pipeline on a minimal dataset. Currently, we don't usually check the results that are produced, but it often catches syntax errors and other serious problems that cause nextflow to exit with an error.
To avoid bloating the workflow, we don't keep test data in the same repository as nf-core workflows. Instead, we use the dedicated nf-core/test-datasets repository.
To set this up, make a fork of that repo to your personal account. Clone the repository and check out a new branch for your workflow:
git clone https://github.com/YOUR_USERNAME/test-datasets.git cd test-datasets git checkout -b MY_WORKFLOW
Now add your test data files - note that they must be very small. GitHub has quite a low file size limit, and the Travis jobs will time out with anything that's not tiny. We typically use PhiX / Yeast / part of a chromosome as a reference and aggressively subsampled input data.
Once added, push these new files to GitHub:
git add . git commit -m "Added test data for MY_WORKFLOW" git push --set-upstream origin MY_WORKFLOW
Finally, make a pull-request against the main nf-core/test-datasets repository with your files. You want this repo to also use a branch with the name of your workflow, so first go to the repository GitHub web page and create this new branch using the UI there. Once created, you can open a pull request and select this as the target branch.
Now that your test data is hosted on the web, you can set up a
test config profile in your
workflow that points to it.
In fact, the
test profile should already exist if you've used the template.
Switch out the example URLs for the ones you added (view the files on GitHub and click 'Raw' to get the URL).
Add any other required parameters so that running the pipeline runs with as few extra
flags as possible. Note that the
test profile can be combined with other profiles such as
conda, so your config should not specify a hardware environment.
Have a go at running the pipeline and see if it works:
nextflow run MY_WORKFLOW -profile test,docker
Note that if you do need to adjust this
nextflow run command, you'll need to update it
.travis.yml config file too.
Ok, so you're essentially finished. Your pipeline is written, the tests pass and you're ready to add your workflow to nf-core.
First, fork your workflow repository to the nf-core GitHub organisation by clicking 'Fork' at the top of the GitHub webpage. If you don't see nf-core as an option, please ask one of the nf-core administrators to do this for you.
Once you have forked the pipeline repository, the nf-core website will automatically update to list your new pipeline.
All nf-core pipelines use branches called
master branch should contain the code from the latest stable release,
dev should have the latest development code.
Before the first release is made we set
dev as the default repository branch instead of
this means that the latest code runs by default up until the first release.
After the first release we switch the default back to
We want people to run the latest development code by default up until the first release.
To do this, we set
dev as the default repository branch.
After a release is created, we set the default branch back to
master so that the default
action is to run the latest stable release code.
Once you have forked the repository, create a new branch called
dev for the active development.
In the repository settings, set
dev to be the default branch.
Remember to configure the repository on the GitHub website with the following:
- A description, the https://nf-co.re URL and lots of keywords!
- Issues enabled, disable Wiki and Projects
- A protected
masterbranch that requires review and passing tests
- Write permissions for
nf-core/alland admin permissions for
You can check that all of these settings are done correctly by referring to your pipeline in the nf-core Repository health web page. This reports the status of various checks and also has the option of fixing errors for you via the GitHub API.
- Open the
social_preview_image_template.svgfile using Inkscape or any other vector graphics editor
- You might need to install the google font Maven Pro
- Update the pipeline name
- If the pipeline name goes beyond the apple, centre the logo in the image
- Update the pipeline description
- Save as
- Export as
- Upload it on the nf-core pipeline GitHub repository in the Social Preview section in the Settings tab
Unfortunately, these steps cannot be automated, as the description of the pipeline could take one or two lines. Line break should look nice and be readable.
If any issue with any of these steps, don't hesitate to contact us on slack #new-pipelines
Just as with your own fork, Travis and Docker Hub need to be set up for the main nf-core fork. You'll need to ask one of the core nf-core team to help you with this.
The main difference when working with the main nf-core fork of your workflow is
that tests for pull-requests against the
master branch will fail. This is because
master branch should only ever contain code from the last release.
Instead, use the
dev branch for new work and always make pull-requests against
that. Then the tests should pass.
When the code is stable and ready for a release, set the
master branch to be the default branch again.
Bump the version numbers on
dev (see below) and make a pull-request from the
dev branch to
master on the nf-core fork.
This is a special case and the tests should pass.
Once they do, merge the PR yourself and let the nf-core team know that you're ready.
When developing the pipeline, the version numbers should be numeric with
dev at the end.
nf-core bump-version command to do this - there are quite a few locations in the
code that need updating and this ensures that it happens in the correct places.
Note that when developing the
:dev tag should be used for docker containers.
When making a release, version numbers should all be numeric. Use
nf-core lint --release
when ready - this will check that everything looks correct.
You are welcome to use any numeric version number, though we recommend using Semantic Versioning.
Ok - now the tough bit - does your workflow stand up to the scrutiny of the nf-core team?! Not to worry, we're a friendly bunch. Let us know about the new pipeline, when you're ready we will create a fake pull-request against the first commit in the pipeline. This gives the PR review interface showing all code that you've written. We will go through everything and request and changes that we think are necessary until you're good to go.
Common things that are flagged at this point are:
- A clear, short but descriptive readme
- Good documentation, especially describing the output files and all parameters
- Pipeline code
We typically tend to have two reviewers for most of the crucial code changes, e.g. adding new major features to an existing pipeline or making an entirely new pipelin release. You can also ping people from the nf-core core team to review your pipelin code by
Once the pseudo-PR is approved, we'll close it and you can go ahead with releasing the pipeline. Put in a basic changelog entry describing the general functionality at release. When you're ready, follow the instructions in the nf-core release checklist.
The nf-core website and helper tools will automatically detect the new release and be updated accordingly.
That's it, you're finished! Congratulations!
Once you've made your first release you can continue to work on your fork and make pull-requests
dev branch on the nf-core repository. Now that we have a stable
there should be reviews of each PR against
dev before merging.
When ready to make new releases, make sure that the version number is increased and create a
master. If tests pass, it can be merged and a new release made.
master branch should always have only the commit from the latest release. This is important
because the commit ID is used to reference whether the pipeline is up to date or not.
We are an open and inclusive community, welcoming any contributions to pipelines already present in nf-core. In many cases, the original developers might either not have experience with some new fancy method or simply doesn't have the time to implement everything themselves - so they might be really happy to see you actively contributing!
Basic rules for such contributions:
- Ask in the Slack channel for the specific pipeline whether there is an open issue on the respective pipeline's issue tracker for the feature you're planning to
- If not, create a new issue there, describing the purpose and ideas you have and wait for someone to comment/discuss
- If everyone is happy or there is some consensus in the community, start implementing the feature in your fork of the respective pipeline
- Please do not write to multiple channels in the Slack community, rather collect all of the information in a single GitHub issue, which makes it also much easier to follow up on your proposal
Sometimes, especially when adding new features to a pipeline, the dependencies change as well. In such cases, you might want to have an updated Docker Container available before submitting a pull request, in order to have the TravisCI tests run through when testing your updated code. To achieve that, please follow these steps:
- Add only the newly required dependencies to the
environment.ymlin the pipeline code
- List this new dependency as something new in the
- Create a Pull Request including only these two changes against the
devbranch of the pipeline you're working on
This way, a review process will be very fast and we can merge the changes into the
dev branch, updating the Docker Image for that pipeline automatically. After ~30 Minutes, the Docker Image for that pipeline is then updated, and you can open your Pull Request containing your actual pipeline code changes.