This has two options. One is the same as `usethis::use_travis`, a vanilla travis config that builds, installs and runs the custom package on travis. The other type of configuration directs travis to build the Docker container (according to the instructions in your Dockerfile) and push the successful result to Docker Hub. Using a Dockerfile is recommended because it gives greater isolation of the computational enviroment, and will result in much faster build times on travis.
use_travis(
pkg = ".",
browse = interactive(),
docker = TRUE,
rmd_to_knit = "path_to_rmd",
ask = TRUE
)defaults to the package in the current working directory
open a browser window to enable Travis builds for the package automatically
logical, if TRUE (the default) the travis config will build a Docker container according to the instructions in the Dockerfile, and build and install the package in that container. If FALSE, the standard config for R on travis is used.
path to .Rmd file that should be knitted by the virtual build environment: default is "path_to_rmd" which causes the function to search for a paper.Rmd file by itself.
should the function ask with yesno() if an old .travis.yml should be overwritten with a new one? default: TRUE