Git can also be used directly within RStudio, meaning the command line can be avoided (if you wish!) for daily use. To get started, you’ll need to have git, R (https://www.r-project.org/) and RStudio (https://www.rstudio.com/products/rstudio/download/) installed. Whilst this option works particularly well for R/coding projects, it can still be used for any type of file or group of folders.
Key steps to get started are:
New Project -
Version Control -
Clone and copy the relevant URL for your repo (use HTTPS if you haven’t set up SSH)
Repository URL and choose where to store the repo on your PC
You may also be prompted for your Gitlab/Github username/password. Your local repo should now be set up on your PC. This will be set up as an R project (https://r4ds.had.co.nz/workflow-projects.html)- this is helpful for cloning/using on multiple computers where all file location paths are relative (not absolute).
To use git within RStudio:
Git tab in RStudio (next to Environment, History, etc.)
Diff to see how each file has changed
Commit. Add text to describe your commit in the
Commit message box and press
Pull (blue down arrow) to check for remote changes to the online repo, and
Push (green up arrow) to send your commits to the online repo.
More information is available at https://happygitwithr.com/rstudio-git-github.html and https://jennybc.github.io/2014-05-12-ubc/ubc-r/session03_git.html.
Top tip (for any git work):
Generally you shouldn’t track extra output files that are generated automatically on each computer (e.g. R project files, R history). Within the main folder of your repo, consider including a text file called
.gitignore.txt which includes a list of file types (or specific files/folders) you wish not to track or upload to your repo. Lots of example templates are available (https://github.com/github/gitignore; see R.gitignore for the R example), and check that you include
*.Rproj. Note: this file, and any changes to it, should be committed to your repo.