I've found migrating ~/library over is problematic even with built in migration assistant, especially if this is their third or later machine being transfered between.

Git is designed with a remote server in mind, just do it that way. Get github or git lab or setup your own remote host.

I tried the same with Google Drive at work and had lots of issues, but recently it seems to have stabilized.

I have my code folders in Dropbox on OSX but I believe my process should work for you. I work in node and have a number of monorepos with nested node_modules folders. I run my idempotent dev-files.command script [2] with or without "--nono" in any monorepo and it handles the entire git aliasing and dropbox folder ignore for node_modules process. I use --nono if I ever need to clear out all of the node_modules and do a fresh pnpm install.

1. https://git-scm.com/docs/gitrepository-layout

2. https://gist.github.com/chiragmehta/a41bd33356b6a2f84075d23d...

The downside is that git history is pretty useful, so it would suck to not sync it.

But you gave a real solution to the problem.

Edit: I remember now that one problem with iCloud was that doing something like switching Git branches or checking out commits causes a catastrophic sync cascade in the code folder itself.

Maybe Dropbox is better at dealing with that kind of thing in general. But that's pretty annoying for any syncing system to deal with, heh.

I guess the simplest solution is to just get into the habit of pushing every little project to github.

you might copy the code working dir in read mode only or whatever idk\

My brother-in-law just accidentally stepped on my laptop and it literally broke into pieces. Fortunately, I have an extra laptop that I can use instead. Please recreate my environment on the new laptop.