It absolutely happens for some organizations. There's industries around it.
And anyway, seems like good practice, and shouldn't be hard to do, and should fit with workflows already familiar from work.
What would be bad practice is to give less-trusted devices (e.g., Linux development phones, or some disposable PC on which I had to install some sketchy software) access to all my files and backups.
Using git this way might be a simple (given we have to know git anyway) way to give the goodness of backups and selectively syncing various kinds of files both ways with the less-trusted devices.
Gitolite/gogs/gitea should all be capable to enforce policies like what you described.
If your concern is data loss/malware, anything on the git level is going to be insufficient (but can still be useful of course, as you said)
I’d echo the suggestion of zfs snapshots replicated on a separate mirror of disks. I can recommend zrepl to set up the snapshotting/replication/pruning part. Syncoid is another popular one.
And anyway, seems like good practice, and shouldn't be hard to do, and should fit with workflows already familiar from work.
What would be bad practice is to give less-trusted devices (e.g., Linux development phones, or some disposable PC on which I had to install some sketchy software) access to all my files and backups.
Using git this way might be a simple (given we have to know git anyway) way to give the goodness of backups and selectively syncing various kinds of files both ways with the less-trusted devices.