Hi Matthew,
> On Aug 20, 2017, at 10:26 PM, Matthew Myint <matthewmyint1...@gmail.com> > wrote: > > Hi, thanks for the transition! Its nice to work from git without the need to > use svn. > > Anyway, I have a couple of questions regarding the usage of git > > 1) When syncing my own GitHub and the Bioconductor git repositories, a check > showed duplicate commits after merging the branches (git log --oneline | wc > returns twice as many commits as in SVN). Is it necessary to follow the steps > in > https://www.bioconductor.org/developers/how-to/git/abandon-changes#force-bioconductor--to-github- > (i.e. forcing changes from Bioconductor to GitHub), or is this fine? I've > also already pushed the merge to Bioconductor git > The bioc-git server should not have duplicate commits. I see that you have already pushed your change, so we will fix the repo for you. Please hold off on all further changes. This effectively contaminates your commit history. It is necessary to follow the steps we outline in the link you mentioned. Once we fix your repo, you’ll have to make that change and commit to your repository again. > 2) Currently, my SSH key provides read/write access to the Bioconductor git > of my team's package. However, we wish to have all the package collaborators > on our GitHub to have similar access. Is this possible, and if so, how would > we go about obtaining this? This is not a good idea, all the development should happen on GitHub, and then one maintainer for the package who has commit access to the Bioc-git server should push these changes upstream. Only the maintainers of the package will have access to the server. > Thank you! > Please give me a day to fix your repository, and I will send you a follow up email. Best Nitesh > Regards > Matthew Myint > Life Science Undergraduate, Year 4 > NUS > > On Thu, Aug 17, 2017 at 4:30 AM, Turaga, Nitesh > <nitesh.tur...@roswellpark.org> wrote: > Hi Maintainers, > > The Bioconductor git server is now alive!! All future commits to Software and > Data experiment packages should be made to the git server. > > Please see the documentation on how to use the new server > https://www.bioconductor.org/developers/how-to/git/. > > If your package has been available through SVN remember to submit your SSH > keys to https://goo.gl/forms/eg36vcBkIUjfZfLe2. > > NOTE: Workflow packages will remain on SVN for the moment. > > Best, > > Nitesh > > > > > > On Aug 7, 2017, at 4:43 PM, Turaga, Nitesh <nitesh.tur...@roswellpark.org> > > wrote: > > > > Hello Maintainers, > > > > > > The details and timeline of the transition from SVN to GIT have been > > finalized. > > > > > > 1. Important Dates, Days of transition - August 15th and August 16th. > > > > August 15th - 9am EST > > > > - Git BETA server commits stop, BETA phase ends. All commits to the > > BETA repository are discarded. > > - Data experiment package SVN commits are stopped. > > > > August 16th - 9am EST > > > > - Software package SVN commits are stopped, > > - About 6 hours after, the GIT server comes to life. > > - No SVN commits here after > > > > August 16th - 6pm EST onwards. > > > > - Only commits to git.bioconductor.org possible. > > - See scenarios on how to commit to the new git server. > > > > (https://github.com/Bioconductor/bioc_git_transition/tree/master/doc) > > > > 2. For access to git.bioconductor.org, please submit your SSH keys to > > > > https://goo.gl/forms/eg36vcBkIUjfZfLe2 > > > > This is important, without which you will not be able to maintain your > > package. > > > > 3. Workflow packages will remain on SVN for the moment. We will inform you > > when the transition of the workflow packages happen. > > > > > > > > Best, > > > > > > Nitesh Turaga > > Bioconductor Core Team > > > > This email message may contain legally privileged and/or confidential > information. If you are not the intended recipient(s), or the employee or > agent responsible for the delivery of this message to the intended > recipient(s), you are hereby notified that any disclosure, copying, > distribution, or use of this email message is prohibited. If you have > received this message in error, please notify the sender immediately by > e-mail and delete this email message from your computer. Thank you. > _______________________________________________ > Bioc-devel@r-project.org mailing list > https://stat.ethz.ch/mailman/listinfo/bioc-devel > This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you. _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
