Search
News: Bioconductor Git/GitHub Mirrors
5
gravatar for Dan Tenenbaum
2.4 years ago by
Dan Tenenbaum ♦♦ 8.2k
United States
Dan Tenenbaum ♦♦ 8.2k wrote:

Dear Bioconductors,

We're pleased to announce the availability of Bioconductor Git Mirrors. 
These are read-only GitHub repositories (available under https://github.com/Bioconductor-mirror
for every Bioconductor software package. These repositories are synchronized with our 
Subversion repository. Package maintainers (or anyone else) can fork these repositories
and do their development on the fork. Complete documentation of the mirrors is at

http://bioconductor.org/developers/how-to/git-mirrors/

These mirrors supersede the Git-SVN bridge, which is now deprecated. 
Creation of new bridges is disabled and maintainers who are using the bridge
should migrate to the Git mirrors as soon as it's convenient, as the bridge
will eventually go away. Instructions for migrating can be found at the above link.

Some features of the new Git Mirrors, and why we feel they are a better solution than the Git-SVN bridge:

  •  The mirrors contain complete commit history.
  •  The mirrors contain release branches for Bioconductor 3.0 and 3.1, and new releases will be added as they happen. You will no longer need  separate repositories for release and devel.
  •  Setup is easy and you no longer have to grant any permissions on your repository to other users. You can commit directly to Subversion using git-svn (https://git-scm.com/docs/git-svn).
  •  Each git commit appears in the SVN log as a distinct SVN commit; commits  are no longer grouped together as they were with the bridge. Each git commit can be mapped to a specific svn commit, and vice versa.
  •   The Git mirrors are much more reliable.
  •   Use is flexible. You can use git locally (without GitHub) or you can use GitHub as well, to take advantage of all its social coding features.
  •  Using GitHub's code search, you can search the entire Bioconductor codebase. Here's a sample search: https://goo.gl/jI92Ys
  •  Subversion is fully supported and remains the cannonical repository; use of Git and GitHub is optional.

We are excited about these new mirrors (brought to you by the hard
work of Jim Hester) and we hope you are too. Questions and comments are
welcome on the bioc-devel mailing list.

ADD COMMENTlink modified 2.4 years ago by Guangchuang Yu800 • written 2.4 years ago by Dan Tenenbaum ♦♦ 8.2k
0
gravatar for Steve Lianoglou
2.4 years ago by
Genentech
Steve Lianoglou12k wrote:

... and there was much rejoicing!

ADD COMMENTlink written 2.4 years ago by Steve Lianoglou12k
0
gravatar for Guangchuang Yu
2.4 years ago by
Hong Kong
Guangchuang Yu800 wrote:

I only run:

 

  1. bash /path/to/update_remotes.sh to setup the git remotes.
  2. Commit to git and push to GitHub as you normally would.
  3. Each time you want to push git commits to svn:
    1. git checkout devel to switch to the devel branch. (use release-X.X for release branches)

When you’re done, be sure and merge any changes from svn back into the git master branch:

git checkout master
git merge devel

 

without other sub-step in step 3 since I though I don't have new commit to push to svn.

 

After that, I am trying to test it with a new commit, but I got the following msg:

Unable to determine upstream SVN information from working tree history

 

 

ADD COMMENTlink written 2.4 years ago by Guangchuang Yu800
1

As the post stated, questions about this should be posted to the bioc-devel list. Please repost this there and include the link to your repository, and please post all commands and their output. Thanks.

ADD REPLYlink written 2.4 years ago by Dan Tenenbaum ♦♦ 8.2k

already sent, thanks.

ADD REPLYlink written 2.4 years ago by Guangchuang Yu800
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.2.0
Traffic: 178 users visited in the last hour