Development is a community effort, and we welcome participation.
Please note that this package is released with a Contributor Code of Conduct.
At https://github.com/ropensci/targets/discussions, you can post general questions, brainstorm ideas, and ask for help. If you are asking for help about a specific issue, please first read https://books.ropensci.org/targets/help.html.
https://github.com/ropensci/targets/issues is for maintenance tasks feature requests. When you post, please abide by the same guidelines as https://books.ropensci.org/targets/help.html.
External code contributions are extremely helpful in the right circumstances. Here are the recommended steps.
Please also follow these additional guidelines.
lint_package()
function from the lintr
package.tests
. Tests that can be automated should go in tests/testthat/
. Tests that cannot be automated should go in tests/interactive/
. For features affecting performance, it is good practice to add profiling studies to tests/performance/
.covr::package_coverage()
. Automated tests should cover all the new or changed functionality in your pull request.devtools::check()
and goodpractice::gp()
NEWS.md
file. Be sure to mention relevent GitHub issue numbers and your GitHub name as done in existing news entries.Authors@R
field of the DESCRIPTION
file.Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.