Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi,
I looked through the known issues and this forum but can't find this anywhere. When I commit an environment to GIT that in my case
a) Turn on native execution engine
b) Adds semtantic-link as a public library
Only the native execution engine setting get's restored when pulling changes into the main dev workspace, I tested this on a different workspace too.
Fabric shows a change it once to commit right after pulling, opening the environment I can see that semantic-link is not listed as a library, adding it removes the detected change compared to the repo.
I git I can see that semantic-link is added to the file Libraries/PublicLibaries/environment.yml:
dependencies:
- pip:
- semantic-link==0.9.0
So that all looks ok to me. Anyone else ran into this and confirm? Otherwise please add it to the bug tracker...
Solved! Go to Solution.
There has been some progress on this, it's now on the known issues list, detailed link here for anybody discovering this conversation:
https://learn.microsoft.com/en-us/fabric/known-issues/known-issue-1025-environment-git-integration-i...
Let's hope it won't take too long to now get it resolved. Will close this thread in the meantime.
Hi @sushiat,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
No unfortunatey not, the solution via the python code is a workaround at best. And for the one or two libraries we are currently adding to our environments fixing it manually is much faster then starting up a spark session to execute the code.
Ideally none of this would be necessary, my goal was to get this reported to the dev team so they can fix the git integration.
Hi @sushiat,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
No it hasn't been fixed, I checked the known issues list this morning and it's not even been added there and definately not fixed. I will update and close this, when an update/fix is released and the issue has been resolved.
Hi @sushiat,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
There has been some progress on this, it's now on the known issues list, detailed link here for anybody discovering this conversation:
https://learn.microsoft.com/en-us/fabric/known-issues/known-issue-1025-environment-git-integration-i...
Let's hope it won't take too long to now get it resolved. Will close this thread in the meantime.
Hi @sushiat,
Thank you for connecting with us!
Could you kindly confirm whether the issue has been resolved? If a solution has been identified, sharing your insights with the community would be greatly appreciated, as it could assist other members facing similar challenges.
Thank you.
Hi @sushiat,
Thank you for reaching the Microsoft Forum Community.
I wanted to check if you had the opportunity to review the information provided by @nilendraFabric. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hello
I have faced this issue.
Give it a try
Create a pipeline step to enforce environment updates:
https://learn.microsoft.com/en-us/fabric/data-engineering/environment-git-and-deployment-pipeline
Could work I guess, but we aren't using deployment pipelines at all. At the moment just have to manually patch it up. Which is currently doable as the number of workspaces we have is still limited, but growing so would be great if it get's fixed so the native git integration restores it correctly.
Try doing this rather than manual pathchup and see the results :
User | Count |
---|---|
79 | |
41 | |
12 | |
10 | |
8 |
User | Count |
---|---|
105 | |
83 | |
28 | |
10 | |
7 |