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) ?
Hi smpa01 ,
Thanks for reaching out to the Microsoft fabric community forum.
Microsoft Fabric's Git integration primarily tracks metadata for Lakehouse artifacts, such as display names, descriptions, and logical GUIDs. It does not track the actual data within tables or files.
Source: Lakehouse deployment pipelines and git integration - Microsoft Fabric | Microsoft Learn
Since Git integration doesn't track actual data, any changes to the data within your Lakehouse won't be reflected in your GitHub repository. This could lead to inconsistencies between your local development environment and the production environment.
In the method you are trying to implement you can go ahead and change the Display name, Description, Logical guid without any potential issues.
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
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