Forum Discussion
Git initialization One lake
When I was asking for git initialization, I was asking about a git init on
\%USERPROFILE%\OneLake - Microsoft\.I actually went ahead and init git on this and so far it has been good.
I can directly add lakehouse folders and folder contents from the vs code workspace and it is convenient cause, I dont need to move away from my development environment to a the cloud (fabric in browser).
Now, are there any negative side effects you might know of that I don't (other than accidental delete of lakehouse folder contents from local that sync to the server instantly but in my case it is git backed up so even more powerful; anything else you can think/know of) ?
When I was asking for git initialization, I was asking about a git init on \%USERPROFILE%\OneLake - Microsoft\.
I actually went ahead and init git on this and so far it has been good.
I can directly add lakehouse folders and folder contents from the vs code workspace and it is convenient cause, I dont need to move away from my development environment to a the cloud (fabric in browser).
Now, are there any negative side effects you might know of that I don't (other than accidental delete of lakehouse folder contents from local that sync to the server instantly but in my case it is git backed up so even more powerful; anything else you can think/know of) ?
Hi smpa01 ,
I’ve looked into potential drawbacks of the approach you're using, but I haven’t come across any documented issues or known limitations specific to that setup but a suggestion I can provide is to regularly monitor synchronization activities between your local environment and the cloud to detect and resolve any issues promptly
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS. Feel free to reach out if you need further assistance.
Thank you