image.png
# tools
j
image.png
j
small issue already reported by @Maxime Garcia , it's because there are TODO statements in the description, build from the readme file. If you have updated your readme file and run
nf-core pipelines rocrate
this should remove the warning
👍 1
j
Huh, I don't see any TODOs in the README... but will try that
m
it could be a leftover TODO
j
Nope
m
an phantom TODO
j
Ah you mean in the ROcrate file/
Regarldess that worked 😄
Should we be changed our default brains from master to main?
The funcscan template is changing that verywhere but we don't have a main branch... should I make one and switch over?
And also should the ROcrate metadata always refer to the latest stable release or the current
dev
?
j
shakefist it should have detected your default branch and used 'master' 😞 you can either switch to main (and be one of the first pipelines testing this 👀 ) or change it on the PR to continue using master
the ROcrate should be from dev, and on every release it will contain the data from master
j
Ok then I switch everything back to master (I think funcscan was one of your manual PRs, so maybe that was a hiccup there rather than automation :)
j
or change it on the PR to continue using master
If I'm not wrong, you can run
nf-core pipelines sync
again and if you have
master
set as the default branch it should be changed automatically. I don't know why it didn't work in the first place
j
OK I can tyr that too
I was actually wondeirng if we should include a change of master branch to main across all pipelines in one go
(is there really any need to have master anbymroe?>
m
I did not follow the procedure with this RO crate branch master/dev/main thingy
j
Whelp, I tried @Júlia Mir 😅
🤣 1
image.png
j
😞 that's the bug I found and why I had to open the PR manually 😅 sorry! it's not fixed yet
j
Sort of scared of touching that now so I think I'll leave it with my module corrections
Hahah ok
good to know, I'll leave it in peace for now then 😬
👍🏻 1