Thanks for your interest in contributing to bioassays. Here are some guidelines to help make it easier to merge your Pull Request:
devtools::test()
to run the teststests/testthat/
If you're new to submitting Pull Requests, please read the section Contribute to other projects in the tutorial A quick introduction to version control with Git and GitHub.
For the most part, I tried to follow the guidelines from R packages by Hadley Wickham. The unit tests are performed with testthat, the documentation is built with roxygen2, and the online package documentation is created with rmarkdown. Continuous integration testing is performed for for macOS by Travis CI, and for Windows by AppVeyor.
The repository contains the files LICENSE
and LICENSE.md
to both adhere to
R package conventions for defining the license and also to
make the license clear in a more conventional manner (suggestions for
improvement welcome). Directories are standard for R packages
as described in the manual Writing R Extensions.
git log
and make sure to reference GitHub
Issues/PRsrhub::validate_email()
. Copy-paste
token from email into R console.rhub::check_on_ubuntu()
rhub::check_on_macos()
rhub::check_on_windows()
devtools::check_win_release()
devtools::check_win_devel()
git commit -am "Bump version: x.x.x.9xxx -> x.x.x and re-build
docs."
git push origin master
and wait for CI builds to passgit tag -a vx.x.x
. Summarize NEWS.md entry into bullet
points. Run git tag -l -n9
for past examples. Push with git push origin
--tags
.R CMD build .
and upload to CRAN submission
site. You will receive an email to request confirmation, then an
email confirming the package was submitted, and then an email with the test
results. Once it is accepted to CRAN, monitor the check results
for any surprise errors. Also, these builds are when the binaries are built for
Windows and macOS, so they aren't available until they are finished. You will
receive an email once all the Windows binaries are available for download
(devel, release, oldrel).Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.