Last updated: 2019-03-10

Checks: 2 0

Knit directory: gt_examples/

This reproducible R Markdown analysis was created with workflowr (version 1.2.0). The Report tab describes the reproducibility checks that were applied when the results were created. The Past versions tab lists the development history.

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: 866f08c

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:    .Rhistory
    Ignored:    .Rproj.user/
    Ignored:    myproject/

Untracked files:
    Untracked:  code/DeletethisFile.Rmd
    Untracked:  code/vertical_table.R
    Untracked:  data/gt_datasets.svg
    Untracked:  trash.Rmd
    Untracked:  trash2.R

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 R Markdown and HTML files. If you’ve configured a remote Git repository (see ?wflow_git_remote), click on the hyperlinks in the table below to view them.

File Version Author Date Message
html 866f08c frm1789 2019-03-10 Add example of colors from viridis
html c18da9a frm1789 2019-03-10 Build site.
html ec56ac6 frm1789 2019-03-10 Build site.
html 2d0d22e frm1789 2019-03-10 Build site.
html a3357ac frm1789 2019-03-10 Build site.
html 4f7442e frm1789 2019-03-10 Build site.
html 323a4bf frm1789 2019-03-09 Build site.
html f44cf75 frm1789 2019-03-09 Build site.
html 7b802ff frm1789 2019-03-09 Build site.
html 89f40a6 frm1789 2019-03-09 Build site.
html 31c611a frm1789 2019-03-09 Build site.
html ccb3d44 frm1789 2019-03-09 Build site.
html 901ba7d frm1789 2019-03-09 Build site.
html dfa77be frm1789 2019-03-09 Build site.
html 5b576d8 frm1789 2019-03-09 Build site.
html 790ab5f frm1789 2019-03-09 Build site.
html 5172a5d frm1789 2019-03-09 Build site.
html f143184 frm1789 2019-03-09 Build site.
html 9375e02 frm1789 2019-03-09 Build site.
Rmd cad473d frm1789 2019-03-09 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.