Thanks for your answer Martin, we will follow your suggestion of using a branch. It sounds the simplest way.
Carlos A. Catania (AKA Harpo) El lun., 31 ago. 2020 a las 14:14, Martin Morgan (<mtmorgan.b...@gmail.com>) escribió: > A reasonable strategy is to create a branch ('master' for submission) that > contains just the package source; use another branch for additional > functionality. > > After submission, your package is cloned to the git.bioconductor.org > repository and you could maintain it from an arbitrary branch in your > repository, so your github 'master' could again contain arbitrary files > (branches are easily renamed in git). > > Martin > > On 8/31/20, 8:11 AM, "Bioc-devel on behalf of Carlos A. Catania (AKA > Harpo)" <bioc-devel-boun...@r-project.org on behalf of harpom...@gmail.com> > wrote: > > Hi to all, > My team is just about to submit a new package to Bioconductor and we > have > a question about the files included in the github repository: > According to > Bioconductor Guidelines for package submission, the repo should not > contain > unnecessary files other than the required for package installation. > However, we have two files in our repo that are not strictly part of > the > package: > > codecov.yml > .travis.yml > > These files are essential for our continuous integration process. I > want to > know if we should remove them before submitting to Bio, or is it ok if > we > left them?. > > Best > > Carlos A. Catania (AKA Harpo) > > [[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