*[HappyGit](https://happygitwithr.com/fork-and-clone.html) gives you the details
*[ohshitgit](https://ohshitgit.com/) may be required here too (but not if you've followed the instructions above)
* 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)
\ No newline at end of file
* 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)
Even more ...
* on [naming files (tidyverse)](https://style.tidyverse.org/files.html)
* coding style, syntax etc. with [lintr](https://github.com/jimhester/lintr)
* set up projects as packages with help from [usethis](https://usethis.r-lib.org/)
* tools for reproducibility
* Is your project file reproducible? [fertile](https://github.com/baumer-lab/fertile) might help
* Or try [rrrpkg](https://github.com/ropensci/rrrpkg) to create a research compendium