Stephanie M. Gogarten
sdmorris at u.washington.edu
Mon Feb 27 17:56:15 CET 2017
After you commit to your github repository, you will need to explicitly
push those changes to svn to get them into Bioconductor devel. I
recommend following the instructions under "Dealing with prior history /
merge conflicts" on this page:
Using the "git cherry-pick" command seems to avoid a lot of errors
others have seen in trying to move commits from git to svn. (At least,
it worked for me.)
If you have not already done so, make sure to run the
"update_remotes.sh" script referenced on that page.
On 2/23/17 9:11 AM, Estefania Mancini wrote:
> Thanks Herve!
> I will try to include test code in the next version of the package.
> By the way, I am a little lost with changes in the package. I want to modify the code of the accepted package and I want to add people to my project in GitHub so I think is better for us continuing using it repository. What do you suggest? I have a version in GitHub, linked to Bioconductor repository. Does commit impact on my devel version of the package? I dont understand clearly where I should commit.
> Thanks in advance,
> De: Hervé Pagès [hpages at fredhutch.org]
> Enviado: lunes, 13 de febrero de 2017 03:15 p.m.
> Para: Estefania Mancini; bioc-devel at r-project.org
> Asunto: Re: [Bioc-devel] covr
> Hi Estefania,
> See here
> for our guidelines to how to add unit tests to your package.
> On 02/13/2017 04:17 AM, Estefania Mancini wrote:
>> I would like to add coverage test to my package. What should I do? Thanks in advance
>> [[alternative HTML version deleted]]
>> Bioc-devel at r-project.org mailing list
> Hervé Pagès
> Program in Computational Biology
> Division of Public Health Sciences
> Fred Hutchinson Cancer Research Center
> 1100 Fairview Ave. N, M1-B514
> P.O. Box 19024
> Seattle, WA 98109-1024
> E-mail: hpages at fredhutch.org
> Phone: (206) 667-5791
> Fax: (206) 667-1319
> Bioc-devel at r-project.org mailing list
More information about the Bioc-devel