-
Notifications
You must be signed in to change notification settings - Fork 37
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
Set publish mode for FastQs #155
Conversation
|
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.
Looks good to me 👍
I think this is good enough for a default config. If users want to avoid copying theses files to save space, they can either set the publish mode to another value or write their own custom config.
Also, looks like the tests are failing because GHA is trying to run them with an old version of nextflow:
- https://github.com/nf-core/demultiplex/actions/runs/6971564442/job/18971897572?pr=155#step:5:442
- https://github.com/nf-core/demultiplex/blob/32b30c84f11866ebeecaa5506006dbd6bb6b75a4/nextflow.config#L242C25-L242C25
demultiplex/.github/workflows/ci.yml
Line 32 in 32b30c8
echo matrix='["latest-everything", "22.10.1"]' | tee -a $GITHUB_OUTPUT
We don't need to test with nextflow 22.10 anymore do we?
Co-authored-by: aratz <[email protected]>
Great catch! Let's see if that fixes it! 🙃 |
I think this was set to avoid duplicate copying of the raw fastqs, and assuming most people would run them through fastp.
I'm not opposed to changing this to only publish if
--skip_tools "falco,fastp"
is set or a param likepublish_fastq
is opted in to.Closes #154