Fix #1208

NEWS.md

@@ -1,6 +1,6 @@
 # targets 1.4.1.9000 (development)
 
-
+* Update the documentation of the `deployment` argument of `tar_target()` to reflect the advent of `crew` (#1208, @psychelzh).
 
 # targets 1.4.1
 

R/tar_target.R

@@ -228,10 +228,13 @@
 #' and the latter conserves local storage.
 #' @param garbage_collection Logical, whether to run `base::gc()`
 #' just before the target runs.
-#' @param deployment Character of length 1, only relevant to
-#' [tar_make_clustermq()] and [tar_make_future()]. If `"worker"`,
-#' the target runs on a parallel worker. If `"main"`,
-#' the target runs on the host machine / process managing the pipeline.
+#' @param deployment Character of length 1. If `deployment` is
+#' `"main"`, then the target will run on the central controlling R process.
+#' Otherwise, if `deployment` is `"worker"` and you set up the pipeline
+#' with distributed/parallel computing, then
+#' the target runs on a parallel worker. For more on distributed/parallel
+#' computing in `targets`, please visit
+#' <https://books.ropensci.org/targets/crew.html>.
 #' @param priority Numeric of length 1 between 0 and 1. Controls which
 #' targets get deployed first when multiple competing targets are ready
 #' simultaneously. Targets with priorities closer to 1 get dispatched earlier