Learning Renv

library(knitr)
library(rmarkdown)

What happens when we change the Rmd file and commit?

In Blog 5 you had the first exposure to Github Actions. We just checked frontmatter compliance (as we do for this round). You see that we have added a second action - here, we are converting the Rmarkdown document to a markdown file by running render_rmarkdown on Github. This action passes successfully for this document. We want to do something similar for blog #4.

Now start reading …

Read the vignette Introduction to renv for the renv R package by Kevin Ushey.

Then do:

1. Install the R package renv on your local machine.

2. In the project for blog 4, initialize the workflow used by the renv package.

3. Add all dependencies to the environment (implicitly by installing all the depepndencies or explicilty by listing dependencies in a DESCRIPTION file).

4. Add the renv folder to your blog 4 repository, and push the changes.

5. Is the github action working? Read any potential error messages in the workflow and try to fix things. Make sure to check stackoverflow for help, don’t forget our Discussion board!

Write a blog post addressing the following questions:

1. What is the idea of the renv package?

2. In 50 to 100 words describe your experience working with renv. What went well? What did not go so well?

Submit this blog post to your blog-6 repo.

1. The idea of the renv package is to help with reproducibility in terms of making sure you or anyone who uses your work knows what packages you are using and what versions of them you are using. And then it will help the user find out where to download those packages as well.

2. Honestly, everything went very smoothly. After downloading ‘renv’ I played around a little bit with a couple of the functions and then I was able to find out what packages were being used in my blog 4 project. Then after that I manually made a Description file for the package dependencies.