In <#3491>, I am adding a GitHub action testing fo...
# tools
m
In #3491, I am adding a GitHub action testing for the sucessful inclusion of configs to the pipeline template. Julia had doubts on its usefulness and while I lean towards having it (without being hellbent), also already thinking of other config functionality we may want to test in the future. Since it is a change in the pipeline template, I don’t want to take this decision without getting more input. What do you think? Is there a value in having a GitHub testing config-related functionality?
m
so it's not a #hill-to-die-on but a #small-mound-i-feel-strongly-about-but-not-enough-to-fight-everyone ?
m
No, more like: I already invested the time, so why not have it then? The computational costs to run a few
nextflow config
commands are relatively low, particularly since the test only runs von release PRs.
j
discussing this with the <!subteam^S08LAB76NBU>, we came out with an idea 😄 So to sum up the concert about adding new CI tests to pipelines is that they block PRs if there is a bug or they start failing for some reason. The suggestion is to run this tests with all pipelines, at a tools level, and open issues if they fail, but not add them to the template.
<!subteam^S08LAB76NBU> please add on anything I have missed
m
So to sum up, I should remove it, correct?
👍🏻 1
m
just a second, i will copy-paste it to the website for the pipeline health check
good now