Sharepoint as repository for shared scripts

I currently consult alongside one other consultant for a company that has a large number of T-SQL scripts stored on a network drive. We RDP to a jump server, launch SSMS, then connect to a database server. The network drive is accessible from our laptops, but not the jump or database servers.

We have been saving local copies of each script (created by a long lost developer) to the jump server with our minor customizations/preferences and agreed to eventually try to come up with some standard shared scripts. The other consultant wants to use GitHub, but neither of us have experience it.

I suggested we create a Sharepoint folder, copy all the existing scripts (within the current folder tree structure so we can find things), then sync to OneDrive on the jump server so that we are always using the same scripts, but they are also backed up and we have access to previous versions.

Any flaws with this idea or reasons to try to get github going?

For additional context, the scripts are used to maintain a system that is scheduled to be sunset this October, but that will likely be around at least another 6 months, depending on how long it takes to get the replacement system up and running.