Skip to content
Prev 20500 / 21312 Next

[Bioc-devel] Moving repository for Bioconductor package

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 <alanmurph94 at hotmail.com> wrote:

            

  
  
Message-ID: <CAGfgtYCefaFKZfHAiPZC6TNVY7B=h3GM+BwMvQfWGt7WNshWUg@mail.gmail.com>
In-Reply-To: <DB9PR03MB97848AEE2F6F7B6AB8BD5BA5B2B42@DB9PR03MB9784.eurprd03.prod.outlook.com>