Originally Posted by Uncle Gizmo
However I'm aware that my efforts would probably benefit from linking Visual Studio Code to Git. Git is everywhere, and seems to be the de facto place for saving backups and the like.
Git is a source code control system. Backups are a side effect of using source code control but not its main purpose. So, I gather, you are unfamiliar with SCC in general.
While Git is very powerful and very popular, it is not the only source code control system around. There are reasons why it is so popular, but on the other hand, I see people struggling with the complexity of Git while they don't actually need it.
Starting to use SCC with Git is jumping in at the deep end.
So, I would recommend learning about SCC benefits and concepts in general before tackling Git. I wrote some stuff on the benefits of source code control
and how to find a suitable SCC-System
. - These texts are focused on Access development, but the basic principles apply generally.
Another recommended starting point is the book Version Control by Example
; by Erik Sink. This book also covers distributed version control and Git in particular.