-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template update #6
Conversation
|
…ine sub-directories
Added a few commits to address issues actually found in sanger-tol/ensemblgenedownload#6 and a commit to enable the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍🏼
I would recommend add the Rapid release website support only warning to the README as well.
Looking at this and gene download workflow, there seems to be a strong case for combining them. The parameters here are a subset of gene download. Most subworkflows are overlapping. And if there is still a need to keep the features apart, this can be easily done with a parameter like --download_type repeat/gene
. The greatest advantage would be not having to maintain 2 very similar pipelines. It can be ensembldonwload
similar to insdcdownload
.
@@ -19,14 +19,6 @@ | |||
|
|||
**sanger-tol/ensemblrepeatdownload** is a pipeline that downloads repeat annotations from Ensembl into a Tree of Life directory structure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the genome is non-ToL, is it still ToL directory structure?
**sanger-tol/ensemblrepeatdownload** is a pipeline that downloads repeat annotations from Ensembl into a Tree of Life directory structure. | |
**sanger-tol/ensemblrepeatdownload** is a pipeline that downloads repeat annotations from Ensembl. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The relevant ToL directory structure for this pipeline is that the output files go into `repeats/ensembl/
Unrelated query: What is this "Run pipeline with test data" CI that keeps running but does not complete? I saw this on |
This is one of the CI requirements we set through the pipeline website health page. Obviously we run it twice with the different version of nextflow, Github doesn't match them. We can add the version to the requirement as well, probably just the latest version? |
I think your comments abut merging the pipelines make sense. I already have the changes regarding |
Closes #4
I've updated the pipeline template from 2.5 to 2.8.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).