From 690595b55d6a79532b2641bc66c4c051c8f50706 Mon Sep 17 00:00:00 2001 From: Ben Anderson <b.anderson@soton.ac.uk> Date: Tue, 7 Jul 2020 14:35:50 +0100 Subject: [PATCH] Update repoAsATemplate.md --- repoAsATemplate.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/repoAsATemplate.md b/repoAsATemplate.md index 23809f1..b3ad822 100644 --- a/repoAsATemplate.md +++ b/repoAsATemplate.md @@ -11,7 +11,7 @@ Things you should touch: | Item | Description | | --- | --- | | **[.gitignore](.gitignore)** | A place to tell git what _not_ to synchronise e.g. `.csv` or [weird OS files](https://gist.github.com/adamgit/3786883)| -| **[analysis/](analysis/)** | Where we store .Rmd files and the .R scripts that call them (usually using a `drake` plan) | +| **[Rmd/](Rmd/)** | Where we store .Rmd files and the .R scripts that call them (usually using a `drake` plan) | | **[DESCRIPTION](DESCRIPTION)** | But only if you use this as a template for your own repo - it is a special file for packages | | **[docs/](docs/)** | Where we put output generated by the .R/.Rmd code. This is helpful if you are using [github/lab pages](https://guides.github.com/features/pages/). Unfortunately the University of Southampton gitlab service does not currently support this. | | **[env.R](env.R)** | Where we store all the parameters that might be re-used across our repo. Such as colour defaults, data paths etc. We avoid using a project/repo level .Rprofile because it can lead to [a **lot** of confusion](https://support.rstudio.com/hc/en-us/articles/360047157094-Managing-R-with-Rprofile-Renviron-Rprofile-site-Renviron-site-rsession-conf-and-repos-conf). | @@ -20,7 +20,7 @@ Things you should touch: | **[R/](R/)** | Where we store functions that get built | | **[README.md](README.md)** | Repo readme | | **[resources.md](resources.md)** | Our collection of guides and `how-tos` | -| **[template.md](template.md)** | This file | +| **[repoAsATemplate.md](repoAsATemplate.md)** | This file | More on data: -- GitLab