Hi @alex.hakso,
Generally, I think the key to using odrive in this way is to ensure that everything is synced and locally cached before acting on the repo. This is going to require some diligence and process. If you end up in a situation where you still have placeholders in the repo structure, or a scenario where a conflict file is created (unsynced changes on an offline system that suddenly comes back online, for example), things are going to start going sideways pretty quick. I would probably recommend not adding .cloud/.cloudf to .gitignore so you have a better chance of knowing when you end up with a placeholder file sitting somewhere in the structure (something I think you should strive to never have in this type of a use case). I wrote a little bit about this in this thread too: ODrive Git Support
As far as storage goes, odrive will try to push the same thing up to all storage. We no longer blacklist any git files, so everything should be going up. The things that may get in the way of this are storage-side restrictions like illegal characters, disallowed extensions, file transformations (like scaling images), etc. Google Drive is pretty flexible, so it sounds like a good target to use.
In the aforementioned thread, I was hoping some folks could chime in on their own best practices. Specifically, I was hoping to hear from those who were requesting that we stop blacklisting git files, but there hasn’t been much feedback on that, so far, unfortunately. I would love to hear about your process if you decide to move forward.