https://nf-co.re logo
Join Slack
Powered by
Did we ever consider linting for nf-core configs?
# infrastructure
j
Did we ever consider linting for nf-core configs?
m
nf-core/configs you mean?
or the config files in nf-core pipelines?
j
The first one
Nd-core/configs
m
so you'd want nf-core linting for nf-core/configs?
because we have nextflow linting you know
what would be the tings you'd want to lint for?
j
What are writing in the specs document: does it specify resources limits, does it have the profile contact etc
😉 1
m
I see what you meant now
j
Much the same as modules etc
Where we will have both
m
So for me this should be directly done in the GHA, since it will probably only be done in this repo
I don't see these linting tests in tools
j
What should be done in GhA??
But I mean with strict syntax we enforce that anyway so that is 'tested' anyway
But the nf-core 'rules' are still enforced via tools in a GHA execution
m
let me wrap up a quick POC
👀 1
test is done stupidly because AI wrote it, and my prompt was stupid, but you get the idea
j
But do we really just want custom bash code inside a GHA? Why not inside tools itself?
Pipelines, modules, subworkflows, configs
m
yeah, so for me this is not necessary in tools
j
But why?
Seems weird to have it somewhere else to ke
m
because the tests you'd want to do is only meant for this single repo
j
No not necessarily
Could be on your fork
Or locally while developing
And theoretically someone could host their own configs somewhere else
m
ok I see what you mean there
Then I think @mashehu should voice his ideas there
😅 1
j
Sorry, the idea was inspired by my comment to you and Pontus saying that configs should be a 'first class citizen'
(even if small)
m
first configs create then lint 🙂 (which makes it possible to do 
lint --fix
)
j
Finnnneeeee
Should see how that's going actually
2 Views
Open in Slack
PreviousNext
Powered by