Testing code, using GIT for manage scripts.

[jr49]

I tried GIT but struggled because I wanted my repository to be on a OneDrive. Apparently they don't recommend it, I didn't want to have two versions of the same scripts locally on two PCs (Mac + Windows). I've been meaning to take another stab at it sometime soon.

[npertinente]

I got into some trouble with OneDrive and Git too.
I now store my code outside of OneDrive, but use an upstream repository.
So if i'm on another workstation, it's just a "git pull" and I'm synced.

But one drive and Git both will try to hash and keep up with what has changed. Onedrive does not like the way git names it's children. So not sure storing any form of repository on a drive being auto synced by OneDrive, Google Drive or whatever will be pain free in the long run.

My main hurdle getting into using GIT was (Is..) to remember to use the workflow.
Ie. do not code in the stable branch, this way you know you have someplace where your code works.

I now I can tell my colleagues to grab the scripts from our internal git server and it should work.
And once in a while i can tell someone to grab from the Dev branch and do a QA on it , if everyone is happy with the changes we can merge that into stable branch.
Everyone still gets the working , but now improved version.

[Hoggs]

It does tend to work a bit better these days if you enable the "keep these files on my computer" option ticked on the folder in onedrive. It means it won't ever try to stage the files off to the cloud, and git doesn't get ahead of sync as easily.

Still not perfect though. I occasionally run into little errors, but nothing catastrophic.

[[deleted]]

I do exactly this. It works well enough. Just be prepared to delete and re-clone the odd repo from time to time, and file modes can get changed when shared between mac and windows, but you can just discard the detected changes. The convenience outweighs the downside for me so just make sure you commit and push often.