https://nf-co.re logo
Join Slack
Powered by
A new request to activate Zenodo for a pipeline ha...
# request-core
u
A new request to activate Zenodo for a pipeline has been made! ā€¢ Pipeline name: nf-core/proteinannotator Core team will activate Zenodo for this pipeline. Please react to the message with āœ… when this is done. [This process is not automated] submitter: @Evangelos Karatzas
šŸ‘€ 1
āœ… 1
m
on it
ā¤ļø 1
It was already turned on by someone else
e
Remind me..does someone need to update the main branch directly with the zenodo id? And also, can you make the main branch the 
main
one again form 
dev
? šŸ˜„
*before I release
m
we cannot get the zenodo id before the release
e
oh true, silly me
m
but I can make the change for the main branch
e
Thanks! I'll prepare the release meanwhole
m
DONE
e
DTWO
šŸ¤£ 1
zenodo id: 10.5281/zenodo.18547736, do we push that directly to main now?
Cite all versions is this one: 10.5281/zenodo.18547735
m
use the one with all the versions
e
opening the v bump with this on dev, and will let you know
šŸ‘ 1
And do you have to copy the zenodo DOI straight into the main now?
m
I haven't done that in a while, but I guess we can just push dev to main
e
better not
coz the version will change to 1.1.0dev..just the zenodo doi from XXXXX in readme where possible (probably rocrate will need an update as well)
I removed the relevant TODO comments
m
oh yeah, we need rocrate and all
facepalm
I am unsure what is the current procedure then
e
This PR should be good enough: https://github.com/nf-core/proteinannotator/pull/76 straight to main, only the zenodo stuff
šŸ‘€ 1
you ll just need to bypass the branch protection rules etc for me šŸ˜„
m
Only because it's you
šŸ˜‚ 1
cowboyhat tip 1
Open in Slack
PreviousNext
Powered by