Can we only publish the trimmed fastqs, rather tha...
# demultiplex
s
Can we only publish the trimmed fastqs, rather than the raw ones too? This doubles the long-term storage at the moment
m
We can have an option for that, sure
I'll whip out a PR
❤️ 1
s
Ping me here when you need a review
m
Can I get one on https://github.com/nf-core/demultiplex/pull/421 before? lingerrings PublishDir is probably messing things up in my current PRs
📝 1
I have replied
Thanks
🙌 1
looking at your comment, I have no issues having this default as true instead of false, I am just wondering what was the actual default in the last release, to see if it's a breaking change or not
s
the default was to publish both
m
Then I'd say let's keep it this way for now
booo 1
Then I need to do a 1.8.0 release instead
Only because it's you
🤣 1
I'll work on this tomorrow
s
its just find + replace for 1.8.0
m
yeah, but a tiny bit more for the current PR, but no worries, I agree that we should have default to produce less data. Data footprint is important
s
you sure you've pushed Maxime?
ah, I see it now 😉
Thanks 🙂
m
sorry, bad connection