And to extend this, we hope to maybe be able to a...
# pipeline-maintainers
j
And to extend this, we hope to maybe be able to automate this somewhat and have nf-core tools linting 'recommend' a version type for you
🤩 4
Right @Júlia Mir? 😬
👌🏻 1
Actually, @Jonathan Manning can you make an issue on tools for tracking?
🙏🏻 1
j
sure
❤️ 1
m
Image from iOS.gif
tux newspaper 5
j
Now you do 😄 (discussed on Friday, I will get to the maintainers minutes soon ®)
e
I missed Friday as well. This makes me really want to fix the Nextflow default rev bug to be able to give it a default tag, and then we have a main branch and cut releases with a single PR review of a version bump and not multiple PRs. Actually, I wonder if we could get around that with just a commit hash for the time being 🤔
m
Anything is better than what we currently have
s
What is the "Nextflow default rev bug"?
p
I don't love that tbh, I was looking at
defaultBranch
recently and the logic is pretty weird and unintuitive.
Like - nextflow has to clone the repo, look at the config file, then check something different out according to what it finds?
Better to just pull the version you want imho and use regular git to define the defaults
Nextflow didn't detect the default git branch until recently, which is why that's there. But we fixed that a few weeks ago, so now if you set the default branch to
main
or whatever else in github, it should correctly pull and check out that.
I was hoping to deprecate and remove
defaultBranch
completely
🤔 1