Source Control / Git Integration - Naming conflict and ID persistence after renaming items

Hello AntoineW 

This has been raised in the past on a post in the forum. Here's the link. 

Solved: Re: GIT integration: azure devop - fabric - Microsoft Fabric Community

This is not a limitation, but a behavior with Fabric and GIT integration. It relates to this - 

When you save a new item in Git, Git integration automatically creates a directory for that item. Once created, Git integration never changes the name of a directory. Even if you change the name of the item, the directory name stays the same.

Git source code format - Microsoft Fabric | Microsoft Learn

The workaround for this is in the original post - 

“Save As → Commit → delete old → Commit”

Every Fabric item (Dataflow Gen2, Lakehouse, etc.) gets a stable internal ID at creation time. Renaming in the UI only changes the display name, not the underlying identity. When you later create another item and give it the old name, Fabric avoids a collision in Git by materializing it with a generated identifier instead of renaming existing folders. As far as I know the only way is to create the new item with the final desired name --> Commit it --> Delete the old item and its Git folder in a controlled change.