From 3d86f32706d3bc4cd617fb3e6c31cbe7399736ee Mon Sep 17 00:00:00 2001
From: Ben Anderson <b.anderson@soton.ac.uk>
Date: Mon, 18 May 2020 12:18:32 +0100
Subject: [PATCH] Update resources.md - added ref to our use of issues (may be
private)
---
resources.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/resources.md b/resources.md
index 12c79a3..a179a97 100644
--- a/resources.md
+++ b/resources.md
@@ -10,7 +10,7 @@
* we don't agree with [keeping your data in your project](https://rstats.wtf/project-oriented-workflow.html#work-in-a-project). Data should be somewhere else, _unless you're a .gitignore wizard_ and your data is small (and non-sensitive/non-commercial/public etc)
* using [git(hub/lab)](https://happygitwithr.com/) for version control (perhaps via [usethis](https://usethis.r-lib.org/) and knowing about [ohshitgit](https://ohshitgit.com/) just in case)
* using [git branches](https://twrushby.wordpress.com/2017/03/27/collaboration-with-rstudio-and-git-using-branches/) as a way for different people to work on the same project without clashing - [ohshitgit](https://ohshitgit.com/) may be required here too
- * using [git(hub/lab) issues](https://guides.github.com/features/issues/) as a way to manage your project
+ * using [git(hub/lab) issues](https://guides.github.com/features/issues/) as a way to manage your project - just like we did for the [new ECCD website](https://git.soton.ac.uk/SERG/sergwebsite/-/issues)
* how to use [drake](https://docs.ropensci.org/drake/) to massively speed up and [manage your workflow](https://milesmcbain.xyz/the-drake-post/). This includes always:
* loading and processing all your data inside a drake plan in a .R file. _So it only gets re-run if the code or data changes_
* creating each of your output objects inside the drake plan. _So they only get re-created if the code or data changes_
--
GitLab