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 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/

Untracked files:
    Untracked:   (tumble-track's conflicted copy 2019-07-09).Rhistory
    Untracked:  DESCRIPTION (tumble-track's conflicted copy 2019-07-09)
    Untracked:  analysis/figure/
    Untracked:  analysis/gwas_pairs.Rmd
    Untracked:  analysis/ldl_cad_cache/
    Untracked:  analysis/simulations.Rmd
    Untracked:  docs/WNAR_2019.pdf
    Untracked:  example_data/chr22_AF0.05_0.1.RDS
    Untracked:  example_data/chr22_AF0.05_snpdata.RDS
    Untracked:  gwas_data/
    Untracked:  ll_v7_notes.Rmd
    Untracked:  src/RcppExports.o
    Untracked:  src/log_likelihood_functions.o
    Untracked:  temp.txt

Unstaged changes:
    Modified:   R/map_pi_rho.R
    Modified:   analysis/about.Rmd
    Deleted:    test_mixSQP.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.