Update module 4: Version control with Git

[jemrobinson]

These changes will be coordinated by @Iain-S

General (applicable to every module)

• Make each module independent of earlier ones (ie. do not rely on examples/specific code from earlier modules)
• Ensure that each module has some small exercises (say 1x 5 min exercise per 45 mins or teaching); add a larger (optional) exercise per course for attendees to complete in their own time
• Update to use more modern libraries and tools (eg. pandas/scipy/numba/poetry)
• Add instructions to the notebooks that you should "Take 5 minutes to do this exercise"
• Add estimated timing information at the top of each notebook
• Switch to a colourblind-friendly colour scheme throughout
• What do you wish people had told you about Python/coding in general?

Module 4: Version control with Git

• Check in advance that people have GitHub accounts with SSH keys setup (see also Add module 0: Setup #83 )
• Note that some command line knowledge is a prerequisite
• Use a vanilla terminal like what the participants will use
  • Should also reference https://explainshell.com/ for looking up what commands are doing
• If switching between text editor/IDE and terminal use light theme for one and dark scheme for another to make it explicit which is which
  • if possible, split screen
• Move theory to beginning
• Decide which commands are most useful (eg. rebase over reset)
• General I had fun getting 60 PRs into the ATI demo repo.
• General I think that this may be too big a module for the time allowed. Working with multiple remotes is quite advanced so maybe the examples/exercises could all be done with a single remote?