Forum Discussion
Issue on Git Commit with Fabric workspace to Github repo
Hi Fabric Team,
We are facing issuing while syncing workspace with github. Got error like 'not able to commit' but it's already in Github repo. But in Fabric workspace, most of SMs and reports are as new items to commit to Git integration. Tried with Disconnect workspace and Connect again. Still having issue. Only that particular workspace is being happened like that. Could you pls advise how to resolve the issue.
Cluster URI https://wabi-west-us-d-primary-redirect.analysis.windows.net/
Request ID bf92b24b-92e0-4595-a562-68af9603b66e
Workload Error Code Git_GitCommitInvalidOperationResultError
Thanks in advance.
Theingi
3 Replies
- v-kathullac
Community Support
Hi TGTun ,
Since the repository is connected to the same workspace, please try the following steps:
- Refresh the Source Control panel and check whether the detected changes are updated.
- Verify the connected repository, branch, folder path, and last-synced commit.
- Compare the workspace items with the corresponding Git files to identify any differences in names, item types, metadata, or folder structure.
- Avoid committing the changes until you confirm why the existing items are being marked as new.
- If the issue persists, share the exact error message and a screenshot of the Source Control panel, including the affected items, for further investigation to microsoft support team.
Below is the link to create a support ticket :
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Reference: Troubleshoot Git integration in Microsoft Fabric
Thanks,
Chaithanya. - TGTunFrequent Visitor
Thanks for your reply. The repo is mapped with that workspace only. No copy from another workspace or not from PBIR.
The empty repo was connected via workspace settings > git integration in that workspace and after quite sometimes, the error is come up. When checking in the repo, looked like all items are already there. The souce control panel was shown as new items to be committed.
- Aditya_Ahire_07Regular Visitor
This is most likely caused by the Logical_id in each item's .platform file doesn't match the workspace items. It happens when the repo items came from another workspace, a copy, or .PBIP.