https://nf-co.re logo
Join Slack
Powered by
No template sync PRs for 4.1.0?
# tools
m
No template sync PRs for 4.1.0?
just wondering if we should do one or not
m
due to non-working runners and then train travel. will start it soon
m
ok no worries
Before you go do it, what is the status of the setup for apptainer, still broken or not?
not in a hurry, enjoy your vacations/days off
m
do you have any pipeline where we can test this quickly with a sync?
m
always
About to have lunch, so I'll try after
m
okay, shouldn't have used seqinspector as a quick test sync, too much customization (what do you have against 
tests/default.nf.test
??)
m
not me for that one
😁 1
and I have nothing against the actual file for tests/default.nf.test, my issue is more with the content 😆
so yeah, I can confirm, it is working, some singularity tests are finished and green
m
do you have a pipeline that is already on 4.0.0 that i can test for a sync?
👀 1
m
#C05GH685FKJ is on 4.0.2
👍🏻 1
I am about to merge 4.0.3
No one should really be using the dev branch of this pipeline, and it only contains back to dev and agent file, plus the manual commit I just did for the apptainer setup, so be my guest and have fun, just don't touch my current PR https://github.com/nf-core/createpanelrefs/pull/92 please
m
you don't use nf-schema or the utlis_nfcore_pipeline subworkflows in createpanelrefs?
m
Replacing by nf-core utils
m
ah, okay. should maybe add these two to the template to make the switch easier 🤔
speaking of that: you should add fastqc to the skip_template features in 
.nf-core.yml
for this pipeline
👍 1
m
Speaking of, I noticed a new script that I think can be replaced by a smart .gitignore
Or I misunderstood the purpose of said script
m
you saw my comment in that pr?
m
No
Sorry
m
the problem is that we don't know how the folder containing 
pipeline_info
is called
m
The one created by outdir
👍🏻 1
Gotcha
I can see why it could be useful for some people indeed
A bit overkill in my opinion, but why not
✅ 1
2 Views
Open in Slack
PreviousNext
Powered by