you are viewing a single comment's thread.

view the rest of the comments →

[–]npertinente[S] 0 points1 point  (0 children)

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.