I happened to look here and realized I'd never answered this. I only make use of the bare bones of what git offers (I have never for example set up a pre or post commit hook) but if you're still looking for resources I noticed that one of the books I grabbed early on is available online free right on the git project's web site (https://git-scm.com/book/en/v2), there's also a list of eleven other books that are available free at https://www.linuxlinks.com/excellent-free-books-learn-git/. I'd also made use of the video tutorial put out by Peepcode, a service I quite miss (they got acquired by Pluralsight) as you weren't locked into streaming but could download the videos and accompanying materials. There's a multitude of stand alone third party git-gui apps, but at this point I generally just use the commandline.
Regarding onedrive, I vaguely recalled hearing warnings about keeping git (and subversion, mercurial, etc) repositories on dropbox and checking now apparently things folder syncing services do to try and be more efficient can result in corrupted code repositories. Googling found a git plugin to sidestep those issues with dropbox and I suspect there are probably tools for other services, but they may be more useful locations for archived snapshots rather than live repos.
While you can set up a github like fancy repository host, you don't need github, gitea, etc. You can point git at any bit of storage you can access by ssh using the style, "git clone ssh://[user@]server/project.git" (quoted from the book linked to above). If you want more than just access via ssh, but still less overhead than one of the web gui tools there's Gitolite, which piggybacks on top of ssh to give something that has fine grained access control or the ability to create new repositories from the command line or get a listing of all the git repos you've created/have access to. It's lightweight enough that for a while back before Covid and spending almost two years working from home I had one running on a micro server (a VPS with only 128MB of memory, a single shared processor core, and a couple GBs of disk) and whenever I would look at the account dashboard barely any of the memory of available cpu cycles were in use. I've had some thoughts of setting it up again, but I'll probably just use straight up git and ssh unless I get really bored and decide to burn a half hour installing it again.
no subject
Regarding onedrive, I vaguely recalled hearing warnings about keeping git (and subversion, mercurial, etc) repositories on dropbox and checking now apparently things folder syncing services do to try and be more efficient can result in corrupted code repositories. Googling found a git plugin to sidestep those issues with dropbox and I suspect there are probably tools for other services, but they may be more useful locations for archived snapshots rather than live repos.
While you can set up a github like fancy repository host, you don't need github, gitea, etc. You can point git at any bit of storage you can access by ssh using the style, "git clone ssh://[user@]server/project.git" (quoted from the book linked to above). If you want more than just access via ssh, but still less overhead than one of the web gui tools there's Gitolite, which piggybacks on top of ssh to give something that has fine grained access control or the ability to create new repositories from the command line or get a listing of all the git repos you've created/have access to. It's lightweight enough that for a while back before Covid and spending almost two years working from home I had one running on a micro server (a VPS with only 128MB of memory, a single shared processor core, and a couple GBs of disk) and whenever I would look at the account dashboard barely any of the memory of available cpu cycles were in use. I've had some thoughts of setting it up again, but I'll probably just use straight up git and ssh unless I get really bored and decide to burn a half hour installing it again.