Hei, I think it is two minor things: • I am waiting for the developer of CAGEr to integrate the last change, so I can rely on the original package instead of local fixes and change the license to MIT. I will also need to change the code a bit so that it uses the package instead of the local changes, and rebuild the container. • There is one linting check at CI that does not pass and I do not know why And the third thing is that I am not sure how the takeover goes

the way I see it, and from what was said on github already, we can rename the old branches and keep them, and just start the dev from scratch on a new dev started from an up to date TEMPLATE

can I merge what we already have at

<https://github.com/ComputationalRegulatoryGenomicsICL/cageflow/tree/104-fit-to-nf-core>

or need to copy paste? There is one more thing, @Slava Sidorov is testing and fixing the pipeline on various parameter combinations, so I will need to merge our dev back to the branch

Yes, I'm still testing and fixing our

dev

and will go through our README soon to make sure that it matches the latest version of the pipeline.

I can see that the first commit here and on the template branch are the same, so we should be good to just transfer all

sounds good, thanks we will make sure that our branch has all the necessary changes and then transfer

let me know if you have issue pushing to the nf-core remote