@@ -136,7 +136,7 @@ common tool to do that is `git`, which is a command line tool but that also has
136136graphical user interfaces for those less keen on the terminal.
137137
138138It is besides the point of this mini-post to explain how to do version control, so we
139- will just refer to [ our Introductory course on Git and GitHub] ( https://imperialcollegelondon.github.io/introductory_grad_school_git_course/ ) .
139+ will just refer to [ our Introductory course on Git and GitHub] [ intro git course ] .
140140For the purposes of reproducibility, understanding the processes and tools described in
141141this course is more than enough.
142142
@@ -168,9 +168,8 @@ specially relevant snapshots of your code - e.g. creating releases - to make it
168168find the right versions with human readable names (e.g. ` v1.0 ` , rather than ` j245er... ` ,
169169which is a commit hash).
170170
171- The same [ introductory course] ( https://imperialcollegelondon.github.io/introductory_grad_school_git_course/ )
172- mentioned above includes instructions on how to use GitHub, so we will not provide more
173- details here.
171+ The same [ introductory course] [ intro git course ] mentioned above includes instructions on
172+ how to use GitHub, so we will not provide more details here.
174173
175174!!! Note
176175 If you want to be a bit more thorough, you should archive the relevant versions of
@@ -186,3 +185,5 @@ and reproducible, but getting started and picking the low hanging fruit is very
186185accessible, takes very little time and can go a long way to support your research. You
187186can always refine things later, adding more tooling and creating a more complex
188187structure for your code. But this is a good place to begin.
188+
189+ [ intro git course ] : https://imperialcollegelondon.github.io/rse_introductory_git_course/
0 commit comments