You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* dev:
Checks if the project looks like an R project and asks for confirmation. #227
Add functionality to force re-installation of all discovered packages and dependencies. #183
Run Travis tests also for NOT_CRAN="false"
Test if logfile exists must be skipped on CRAN #225
Add function to list checkpoint archives and remove archives #228
Copy file name to clipboardExpand all lines: R/checkpoint.R
+57-12Lines changed: 57 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,11 @@
53
53
#' @param scan.rnw.with.knitr If TRUE, uses \code{\link[knitr]{knit}} to parse \code{.Rnw} files, otherwise use \code{\link[utils]{Sweave}}
54
54
#'
55
55
#' @param verbose If TRUE, displays progress messages.
56
+
#'
57
+
#' @param forceInstall If TRUE, forces the re-installation of all discovered packages and their dependencies. This is useful if, for some reason, the checkpoint archive becomes corrupted.
56
58
#'
59
+
#' @param forceProject If TRUE, forces the checkpoint process, even if the provided project folder doesn't look like an R project. A commonly reported user problem is that they accidentally trigger the checkpoint process from their home folder, resulting in scanning many R files and downloading many packages. To prevent this, we use a heuristic to determine if the project folder looks like an R project. If the project folder is the home folder, and also contains no R files, then \code{checkpoint()} asks for confirmation to continue.
60
+
57
61
#'
58
62
#' @return Checkpoint is called for its side-effects (see the details section), but invisibly returns a list with elements:
0 commit comments