Last updated: 2020-07-20
Checks: 2 0
This reproducible R Markdown analysis was created with workflowr (version 1.6.2). The Checks tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.
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.
Great! You are using Git for version control. Tracking code development and connecting the code version to the results is critical for reproducibility.
The results in this page were generated with repository version ff54d1d. See the Past versions tab to see a history of the changes made to the R Markdown and HTML files.
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_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/ Unstaged changes: Modified: analysis/style.css Staged changes: Modified: analysis/_site.yml New: analysis/style.css
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.
These are the previous versions of the repository in which changes were made to the R Markdown (
analysis/license.Rmd) and HTML (
docs/license.html) files. If you’ve configured a remote Git repository (see
?wflow_git_remote), click on the hyperlinks in the table below to view the files as they were in that past version.
|html||5369804||Damon Bayer||2020-07-19||Update 2020-07-19|
|html||65c7195||Damon Bayer||2020-07-16||theme change|
|html||66110a1||Damon Bayer||2020-07-14||Initial Proof of Concept|
|Rmd||6151dc8||Damon Bayer||2020-07-14||Start workflowr project.|
What license are you using for your code? See choosealicense.com for help deciding. It’s a convention to save a file
LICENSE in the root of your Git repo that contains the license text.
What license are you using for the written content on your site? It is traditional to choose a Creative Commons license for this type of content.
How should others cite your work? It’s a convention to save a file
CITATION in the root of your Git repo that contains the citation information.