Not to scare you away, but the real complication starts when you work with other people on same Git repo, with multiple branches.
Using it as a single user is pretty much no brainer - now that I have beeen using it for a few months. 
You know where to find me when you can't resolve conflicts. 
Yup, Sid, I got you on Skype, there is no escape, haha.
To be honest I think my initial scare with GIT was because I kind of started Docker at the same time as I was exploring GIT and with Digital Ocean saying it could get its deployment directly from GIT etc. I found it all a bit intimidating, however now I have made about 30 Digital Ocean projects that all makes perfect sense to me, and I can worry only about GIT as a separate entity. Also to be honest I could not see why I would need it, considering I have not even seen another human being in about a month, I am kind of a working one man band as well as in real life too, like a happy hermit crab.
By the way, sorry @Antony, I seem to have steered your topic off the beaten track twice in a single thread.
Thank you for that very clear tutorial. I am also one that is very afraid of GIT. Your videos show how it can be very useful. I will have to dive in. I do currently use GIT to save versions at certain stages of my project but the idea of branches is scary. I will now set up a sandbox project and try to see if I can confuse myself even more. 
This is what I have. Is it a good start? Also pushes to Github.
@brad, how do you have the version numbers next to each commit? Looks interesting and not something I’ve done. How does that work?
Version numbers are just simple tags. I put them there so I can see if it was a significant update or just a small update based on version numbers. They don’t really do anything they are just for my reference.
Aah, so you just use the ‘add tag’ option for each commit?
Yes, there is probably better uses for the tagging. But these do at least mean something to me.
In GIT is is standard to keep version numbers with tags.
