Last updated: 2018-09-04

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: ed98c23

  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:    data/.DS_Store
  
  Untracked files:
      Untracked:  .Rbuildignore
      Untracked:  analysis/mapping.Rmd
      Untracked:  data-raw/
      Untracked:  data/csv/
      Untracked:  data/raster/
      Untracked:  data/sf/
  
  Unstaged changes:
      Modified:   analysis/index.Rmd
      Modified:   analysis/vector.Rmd
  
  

  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	bba1865	annakrystalli	2018-09-04	Build site.
Rmd	6afbfe5	annakrystalli	2018-09-04	workflowr::wflow_publish(c(“analysis/further_resources.Rmd”))

---

---

This reproducible R Markdown analysis was created with workflowr 1.0.1

---