Yes, if git remote -v
lists something like famat master$ git remote -v upstream g...@git.bioconductor.org:packages/famat (fetch) upstream g...@git.bioconductor.org:packages/famat (push) then `git push upstream master` will push the changes on your current local branch to the master branch of the Bioconductor git repository. Remember (1) increment the version (to 0.99.9, 0.99.10, ...) so that the successfully built package will propagate to the repository that makes it available to users. (2) your accepted package is built using the *NIGHTLY* builder, so your changes will only appear after the date & time that you make the commit are before the 'Snapshot date' on the build report for your package at https://bioconductor.org/checkResults/3.12/bioc-LATEST/famat/ -- this can be 24-48 hours after you actually make your commit. Remember to check your commits locally before waiting for the build report ... R CMD build famat R CMD check famat_0.99.9.tar.gz (or more precisely with the instructions linked from the build report for your package). Martin On 10/24/20, 4:26 PM, "Bioc-devel on behalf of Emilie" <bioc-devel-boun...@r-project.org on behalf of emiseche...@gmail.com> wrote: Hello, My package (famat) had an error while being tested in the nightly devel build. I fixed the issue, but i have a naive question : do i just have to push changes using "git push upstream master" like before? And will the build be launched again after that? Thank you for your answer Emilie [[alternative HTML version deleted]] _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
