Last updated: 2018-05-23

workflowr checks: (Click a bullet for more information)
• R Markdown file: up-to-date

Great! Since the R Markdown file has been committed to the Git repository, you know the exact version of the code that produced these results.

• Repository version: 53fc845

Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility. The version displayed above was the version of the Git repository at the time these results were generated.

Note that you need to be careful to ensure that all relevant files for the analysis have been committed to Git prior to generating the results (you can use wflow_publish or wflow_git_commit). workflowr only checks the R Markdown file, but you know if there are other scripts or data files that it depends on. Below is the status of the Git repository when the results were generated:

Ignored files:
Ignored:    .DS_Store
Ignored:    .Rhistory
Ignored:    .Rproj.user/
Ignored:    figure/.DS_Store
Ignored:    figure/ch02/.DS_Store


Note that any generated files, e.g. HTML, png, CSS, etc., are not included in this status report because it is ok for generated content to have uncommitted changes.
Expand here to see past versions:
File Version Author Date Message
html 79a1ea4 John Blischak 2018-05-23 Build site.
Rmd 3e36241 John Blischak 2018-05-23 Update to 1.0
html 3e36241 John Blischak 2018-05-23 Update to 1.0
html 17de7de John Blischak 2018-01-11 Build site.
Rmd 93052d7 John Blischak 2018-01-11 Apply workflowr infrastructure. Committed files manually.

I’m John Blischak. I work with Matthew Stephens at the University of Chicago to develop software and lesson material to support reproducible research.

This reproducible R Markdown analysis was created with workflowr 1.0.1