rworkflows works by calling a centralized action (stored here) from which users can activate/deactivate certain features with the arguments in the short rworkflows.yml script.
Currently, I've set the arguments such that rworkflows will:
build and check taxize for CRAN standards using rcmdcheck.
build a docker container with taxize and all its deps installed, and store it on the GitHub Container Registry (under "Packages" on your GH repo). If you like, you can also add instructions for how to create an image from this container via rworkflows::use_vignette_docker() (though I'll leave that up to you in the interest of keeping this PR simple).
builds and launches a pkgdown website on GH Pages. Though I noticed your docs page is hosted elsewhere (a feature rworkflows doesn't yet support), so if you'd like to turn this step off just set run_pkgdown: ${{ false }} (or I can do this for you in the PR if you like).
Let me know if you have any questions or requests for changes the meantime!
taxize 0.9.101
Previously discussed here:
https://github.com/ropensci/taxize/issues/924#issuecomment-1883980733
Add
rworkflows
.rworkflows
.taxize
version.rworkflows
status badge to README.rworkflows
works by calling a centralized action (stored here) from which users can activate/deactivate certain features with the arguments in the short rworkflows.yml script.Currently, I've set the arguments such that
rworkflows
will:taxize
for CRAN standards usingrcmdcheck
.taxize
and all its deps installed, and store it on the GitHub Container Registry (under "Packages" on your GH repo). If you like, you can also add instructions for how to create an image from this container viarworkflows::use_vignette_docker()
(though I'll leave that up to you in the interest of keeping this PR simple).run_pkgdown: ${{ false }}
(or I can do this for you in the PR if you like).Let me know if you have any questions or requests for changes the meantime!