> Secondly, does anyone have a good approach for keeping a mirror of it at the > url in the lab's github since this is the link we reference in the > publication: https://neurogenomics.github.io/MungeSumstats?
Maybe an alternative is to: 1. Transfer the existing repo to your GitHub name 2. Fork the repo in your GitHub name to the 'neurogenomics' GitHub organization That way, it should be visible to users visiting https://github.com/neurogenomics/MungeSumstats that there is an upstream repo available. Disclaimer: I'm not sure if Step 2 will be possible after the transfer, because GitHub tend to provide re-directs for transferred repos. Just a though ... /Henrik On Fri, Jul 26, 2024 at 3:59 PM Mike Smith <grimbo...@gmail.com> wrote: > > Dear Alan, > > I don't think there are any formal steps required to do this. Once a > package is in Biocondcutor, it is effectively decoupled from whatever Git > repository it was originally submitted from. For example, you could delete > the existing GitHub repository entirely, and it wouldn't affect the version > hosted by Bioconductor. So really you can do as you like with the GitHub > repositories. > > Currently the only real link is established by you, as the maintainer, > making sure that changes are pushed to both GitHub and Bioconductor > repositories. You probably do that manually, by running two git push > commands with different remotes. One option here would be for you to fork > the repository from the Neurogenomics organisation into your personal one. > Then set that new GitHub repository as a remote on your local copy - maybe > setting that as 'origin' and replacing the current one. You can then use > that as the default place to develop the package. > > If you don't make too many changes then I think the simplest option to > maintain a mirror is to simply have three remotes for your repository: > origin (personal GitHub), bioc (git.biocondutor.org), lab_mirror > (Neurogenomics GitHub). Then every time you push a change to Bioconductor, > also push it to the 'lab_mirror'. It's one more step, but maybe not too > much of a burden if you're not doing it frequently. Alternatively you > could set up a GitHub action in one repo that would push to the other, > probably using something like this https://github.com/repo-sync/github-sync > > On Fri, 26 Jul 2024 at 14:02, alan murphy <alanmurp...@hotmail.com> wrote: > > > Hi all, > > > > I'm the maintainer for MungeSumstats< > > https://github.com/neurogenomics/MungeSumstats> package and I will be > > leaving my current lab in the near future. Currently, the package code is > > hosted in the lab github but I want to move it to my personal github - What > > are the steps for setting up upstream git push to Bioconductor once I move > > it? Secondly, does anyone have a good approach for keeping a mirror of it > > at the url in the lab's github since this is the link we reference in the > > publication: https://neurogenomics.github.io/MungeSumstats? > > > > Cheers, > > Alan. > > > > [[alternative HTML version deleted]] > > > > _______________________________________________ > > Bioc-devel@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/bioc-devel > > > > [[alternative HTML version deleted]] > > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
