Hello! The <!subteam^S08LAB76NBU> plan is to relea...
# pipeline-maintainers
j
Hello! The <!subteam^S08LAB76NBU> plan is to release a new version of nf-core/tools before the hackathon, and if everything goes as expected we will start testing it next week. To try and make the template updates smoother and pick up possible errors beforehand, we are introducing a testing step where we will ask for a volunteer to do a template update and report their experience or possible errors before we trigger the sync PRs to all pipelines. Who wants to sacrifice their first born volunteer their pipeline for this?
👋 2
m
#C01NHS4CC91 and #CGFUX04HZ volunteer
🎉 3
j
@Maxime Garcia we just triggered a sync PR to rnavar and sarek
@James Fellows Yates we just triggered a sync PR to cratetaxdb
you will receive PRs very soon! you can go through the template update and let us know if you find something suspicious 👀
j
salute
Once I've done createtaxdb, and all fine, maybe do mag too
As a true test 😆
m
please let me do resolve of merge conflicts in createtaxdb so we can record them 🙂
j
OK!
I let you do that, and you send me draft and I try to appl yto mag?
👍🏻 1
j
On my todo for tomorrow! Kid caring time now
👍🏻 1
m
we are anyway working on a patch release for tomorrow (shouldn't affect anything on your side)
m
I was in a meeting the whole afternoon, sorry I couldn't look at it
j
Btw @mashehu I find the blog post really hard to read
image.png
With the use of code blocks in titles
e.g. when I read the 'resolution' section of ,nf-core.yaml I think the website is just rendering halfway the lines for the awstest.yml file wierdly
m
good point
j
Better! I would maybe put
**Description**
above each description, so you can better see the difference between that and the
Resolution
Otherwise I find it much easier to comparmentalise 🙂