I just learned that last year, too, when my last employer did not have any versioning tool whatsoever, except windows network shares (yes, there are more than enough companies that do it that way. It's the second time i encountered such a horror scenario). So I just set up a bare git repository on the network share and used this to keep my project there. Glad they understood that git does make sense and setup a gitlab server soon after.

After all it seems kinda obvious, but hey.

I learned that from a different article posted here last week :) https://jeremymikkola.com/posts/2017_07_15_move_commits_betw...

I had to set up an entire government team's workflow that was required to be isolated completely from any network. I had to create multiple remotes that were filepaths that pointed to specific USB drives. Depending on which USB drive was connected to their laptop, a developer was able to push and pull any changes to their codebase.

It felt unintuitive at the time but thinking back, this team was able to produce code much faster than other teams that didn't have a similar workflow set up.

Another cool thing that I believe git does in these situations is that it hard-links the blobs in the .git folder if you do a local clone. It makes sense: the blobs are immutable and content-addressed, no need to store two copies! Just have two links to the same file system object, save a bunch of disk space.