The release process goes to CRAN. Details on how the release is prepared need to be formalized and documented.
If interested in contributing, please read CONTRIBUTING.md
We use GitHub Actions for the build process. Files can be seen in the ./workflows directory.
We modify the examples from the r-lib/actions repository for our purposes as follows:
workflows
folder
consistent for historyR-CMD-check
is the analogue of check-full
, without devel
R. It
approximates CRAN submissiontest-coverage.yaml
and pkgdown.yaml
both have lines added to set
appropriate environment variables for "integration tests" and run Connect in
order to evaluate the package (and product) more thoroughlyintegration-tests.yaml
, which is analogous to R-CMD-check
but with integration tests tooIntegration tests are designed to run the connectapi
package against the
actual latest version of Connect
build_test_env()
functiondocker compose
to build an environmenttests/integration
directorytest-integrated.R
script, and keys mostly on the
CONNECTAPI_INTEGRATED=true
environment variableTo run integration tests interactively / locally run the following:
connectapi:::build_test_env()
readRenviron(".Renviron")
# or set this in .Renviron yourself
Sys.setenv("CONNECTAPI_INTEGRATED"="true")
# or run R CMD CHECK with that env var set, etc.
source("tests/test-integrated.R")
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.