Forum Discussion
GitHub integration not showing all branches
Hi! I've tried connecting a workspace to GitHub. I have permissions in the repository and have generated a personal access token. Connection succeeds, but when I want to browse branches, I can only see exactly 30. Always the same 30 (mainly old ones). When searching for branches by name, no other branches are revealed. I've read that the GitHub API has a limit of 30 items per page, so wondering if this is the reason? I used the same personal access token in Databricks and could then see all branches, so I don't suspect permissions is the problem.
This becomes an issue whenever you have 30 branches or more, as that means some won't be available to base a new branch off of or switch to. You can of course question if there should ever be more than 30 branches in a repo, but still. Anyone else have the same experience or know of any solutions?
Thanks in advance,
Pontus
Hi, sorry for not updating this thread. Yes, they confirmed it was a bug and that it would be fixed during last week, and indeed checking now it is fixed - I see every branch.
8 Replies
- lbendlinSuper User
Examine the data you get back. There should be a continuation token that you have to use until it is fully consumed.
- PontusPerssonAdvocate I
This is in the Fabric workspace GUI, when using Git Integration and selecting/browsing branches. I'm not making the API calls to GitHub myself
- lbendlinSuper User
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
- AnonymousNot applicable
Are you using a fine-grained personal access token or a classic token? I haven't used that yet, I'd like to test if I can reproduce the same issue.
Best Regards,
Jing- PontusPerssonAdvocate I
Hi, classic token. I was not able to get it to work with fine-grained but that problem could be on my end.
I've also opened a ticket about this
- AnonymousNot applicable
Have you received any response from the support ticket? Is there any solution for it?
Best Regards,
Jing