This outlines how to propose a change to bpmodels.
If you want to make a change, it's a good idea to first file an issue and make sure someone from the team agrees that it’s needed. If you’ve found a bug, please file an issue that illustrates the bug with a minimal reprex (this will also help you write a unit test, if needed). See bug report template. If you have a feature request see feature request.
Fork the package and clone onto your computer. If you haven't done
this before, we recommend using usethis::create_from_github("epiverse-trace/bpmodels", fork = TRUE)
.
Install all development dependencies with devtools::install_dev_deps()
,
and then make sure the package passes R CMD check by running devtools::check()
.
If R CMD check doesn't pass cleanly, it's a good idea to ask for
help before continuing.
Create a Git branch for your pull request (PR). We recommend using usethis::pr_init("brief-description-of-change")
.
Make your changes, commit to git, and then create a PR by running usethis::pr_push()
, and following the prompts in your browser.
The title of your PR should briefly describe the change.
The body of your PR should contain Fixes #issue-number
.
For user-facing changes, add a bullet to the top of NEWS.md
(i.e. just
below the first header). Follow the style described in https://style.tidyverse.org/news.html.
New code should follow the tidyverse style guide. You can use the styler package to apply these styles, but please don't restyle code that has nothing to do with your PR.
We use roxygen2, with Markdown syntax, for documentation.
We use testthat for unit tests. Contributions with test cases included are easier to accept.
Please note that bpmodels
is released with a
Contributor Code of Conduct. By contributing to this
project you agree to abide by its terms.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.