I’m using it in a business setting, and hate it. Our company has lost about a thousand hours of work from OneDrive corrupting git repos. Everyone at the company is aware that you must NEVER allow OneDrive to touch a git repo, but OneDrive keeps adding directories without consent or notification, so people’s git repos keep getting corrupted.
Maybe it’s the IT department, or maybe Onedrive just sucks.
OneDrive doesn’t take over directories without being told to. And specifically, it’s “Known Folders Move” system, only does Documents, Desktop, and Pictures. If KFM is being turned on without user consent, that is IT’s fault. If it is including folders outside those 3? Also IT’s fault.
It corrupting git repos? Not sure on that one. It doesn’t feel like OneDrive should be doing that, but it does struggle with unusual read/write patterns, so I’m guessing the way git is working doesn’t resemble a standard file saving, and Microsoft being full of developers and owning github should probably be accounting for that use case.
I’m using it in a business setting, and hate it. Our company has lost about a thousand hours of work from OneDrive corrupting git repos. Everyone at the company is aware that you must NEVER allow OneDrive to touch a git repo, but OneDrive keeps adding directories without consent or notification, so people’s git repos keep getting corrupted.
Maybe it’s the IT department, or maybe Onedrive just sucks.
OneDrive doesn’t take over directories without being told to. And specifically, it’s “Known Folders Move” system, only does Documents, Desktop, and Pictures. If KFM is being turned on without user consent, that is IT’s fault. If it is including folders outside those 3? Also IT’s fault.
It corrupting git repos? Not sure on that one. It doesn’t feel like OneDrive should be doing that, but it does struggle with unusual read/write patterns, so I’m guessing the way git is working doesn’t resemble a standard file saving, and Microsoft being full of developers and owning github should probably be accounting for that use case.