Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
This seems like the issue mentioned in the link below, except for us it's only semantic models, and it's November, not March, and we've been using git for several months now. I'm guessing it's the same cause as well, an update to how git stores files? Is the solution still to change our repo to accept changes from the workspace and then accept/commit the changes in the workspace? Is this a problem that's going to keep coming up? Or is this something completely different?
Solved! Go to Solution.
Hi @c_lovestrom ,
The issue is due to the new changes introduced for the new git system files and the corresponding version bump on the report artifact definition based on the Feature switch. We are currently investigating a fix to address the issue that would prevent causing git diffs with the new system files. Current workaround steps is to commit the changes and resolve conflicts. Known issue - Git integrated workspaces incorrectly show status of Uncommitted - Microsoft Fabric | ...
Thank you for your understanding and support.
Best regards,
Mengmen Li
Hi @c_lovestrom ,
The issue is due to the new changes introduced for the new git system files and the corresponding version bump on the report artifact definition based on the Feature switch. We are currently investigating a fix to address the issue that would prevent causing git diffs with the new system files. Current workaround steps is to commit the changes and resolve conflicts. Known issue - Git integrated workspaces incorrectly show status of Uncommitted - Microsoft Fabric | ...
Thank you for your understanding and support.
Best regards,
Mengmen Li