Forum Discussion

skiganesh's avatar
skiganesh
Frequent Visitor
1 day ago

Git Commit Issue

Hello Fabric Community, 

I have a workspace that is connected to my GitHub repo. I used a personal access token to integrate GitHub with Fabric. Initially, I created the token for only one day and committed my items to GitHub. When I connected my GitHub repo again with a new token, I was unable to commit the changes that had been made so far because I could not find any items pending to commit in the source control pane "Changes" tab. PFA.

Please suggest a solution or let me know the proper way to integrate my changes into GitHub again. 

Thanks in advance for any insights or guidance!

 

4 Replies

  • Did you get a prompt about synchronizing items after configuring the Git integration again?

  • Hi skiganesh, this usually comes down to the reconnect and not the items themselves. After you connect again with a new token, check three things. First, that the new personal access token has read and write access to repository contents for that repo, since a read only token will show items but not allow a commit. Second, that you reconnected to the same repo, branch and folder as before, because Fabric compares your workspace to the connected branch and folder, and a different folder can make everything look unchanged or out of sync. Third, open the Updates tab, because if the branch has commits that the workspace has not pulled yet you need to update first before the Changes tab lets you commit. If it still shows nothing, disconnect the workspace from Git, reconnect to the right branch and folder, and choose to sync the workspace content with the branch when prompted. Making a small edit to one item also helps confirm that change detection is working.

    AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.