Anyone knows about <#C0493FQQZ3P> workflow? It see...
# nostupidquestions
p
Anyone knows about #C0493FQQZ3P workflow? It seems abandoned? I found several problems (some serious bugs) but it seems that it's left on its own...
s
It can happen that pipelines become orphaned. You are welcome to start contributing though, if you need someone to help review your PRs then we can find someone to do that.
p
Thanks! The code heavily uses deprecated syntax so doesn't work with nextflow 26+. That requires a massive refactoring. I can do that if it's ok.
🙌 1
That issue also blocks the CIs, any PR doesn't pass with latest-everything.
s
Basically the pipeline belongs to the community. If you wish to start to contribute, you are welcome
If you are willing to do it, go for it! You may want to post on the #C0493FQQZ3P channel, to see if anyone else is able to join your effort.
p
Sounds good! Thanks for the tips
s
But to reiterate, please ping on #CQY2U5QU9 to get someone to look at your PRs, and we can support you getting the pipeline up to date. A template merge will likely help with some of the strict syntax, although the most recent automated template PR is 3.3.1? @mashehu?
👍 1
p
I've been able to update to the latest template, but there's still a lot of work to do to for the deprecated syntax. I'll also match the latest versions of nf-core modules and subworkflows.
🙌 1
s
I'd highly recommend doing discrete PRs (apart from the template merge), they are earlier to review and merge
p
Ok, I'll do 🙂
Now it seems that linting is fine, the major work is now to fix the pipeline. I'll open follow up PRs.
s
Please focus on getting a version that is running on CI, then do any actual fixes to logic. I see that https://github.com/nf-core/rnasplice/pull/195/ incorporates a lot of module/subworkflow updates, that is an example of things that are easier to review separately.
p
yes, many of these were necessary to pass the linting.