nf-core should support private repos that are not on GitHub about tools HOT 2 CLOSED

Hi @stevekm,

We built and continue to build the nf-core tooling primarily for the nf-core community and it's pipelines, which reside only on GitHub. However, we are doing our best to slowly move the codebase towards more general use for the wider Nextflow community. This includes providing support for other Git providers.

currently private custom modules repo's only work if you are hosting them on GitHub
The fact that only GitHub is supported (?) seems weird and arbitrarily restrictive.

Your assertions here are incorrect. We explicitly do support other Git providers for modules. In fact we have code tests in the CI that work with an nf-core organisation on GitLab specifically to ensure this compatibility: https://gitlab.com/nf-core

If you've found a case where this doesn't work for whatever reason, please open an issue specifically for that error with a reproducible example. Or better still, submit a PR to fix the problem.

Issue #2406 that you linked to is about downloading pipelines, not working with modules. That's a much older part of the nf-core/tools codebase and much of it dates to before we aimed to support anything other than nf-core pipelines. It also includes complexities such as fetching the nf-core shared configs which are not generalisable. We could look into extending the relative recent --tower functionality that uses git clone if needed, but let's take that discussion on that thread.

It's probably not surprising that the vast majority of active contributors to nf-core, especially the core tooling, are people who are use nf-core pipelines in their day to day work. We would love more contributors to nf-core/tools who work with pipelines outside of that scope. You're welcome to join us :)

from tools.

thanks for the clarification!

from tools.