Should we create a renv/ folder automatically if consent exists?

[zkamvar]

On the release of 0.0.0.9050, I noticed that the documentation site, which did not previously have a {renv} folder, was creating the folder in continuous integration, despite the lesson not having a {renv} folder itself:

  ℹ Consent to use package cache provided
  * "~/Library/Caches/org.R-project.R/R/renv" has been created.
  → Searching for and installing available dependencies
  * Discovering package dependencies ... Done!
  * Copying packages into the cache ... [16/18] ��������[17/18] ��������[18/18] Done!
  → Recording changes in lockfile
  The following package(s) will be updated in the lockfile:
  
  # CRAN ===============================
  - base64enc   [* -> 0.1-3]
  - digest      [* -> 0.6.27]
  - evaluate    [* -> 0.14]
  - fastmap     [* -> 1.1.0]
  - glue        [* -> 1.4.2]
  - highr       [* -> 0.9]
  - htmltools   [* -> 0.5.2]
  - jquerylib   [* -> 0.1.4]
  - jsonlite    [* -> 1.7.2]
  - knitr       [* -> 1.34]
  - magrittr    [* -> 2.0.1]
  - renv        [* -> 0.14.0]
  - rlang       [* -> 0.4.11]
  - rmarkdown   [* -> 2.11]
  - stringr     [* -> 1.4.0]

I don't know if this is the correct behavior. On the one hand, it will slightly increase the deploy time for the lesson, on the other hand, it means that new packages added to the lesson will be discovered and rendered online.

[zkamvar]

As a followup, the folder is being created if the lesson uses R markdown unless the user explicitly states no_package_cache().