Repository navigation
Plugin no longer gives access to GitHub issues while using personal account. #9064
Agent suggestions
Public previewDescription
Visual Studio Code version: 1.141.2
GitHub Pull Requests version: > 0.166.1
This involves a personal GitHub account with a ditto personal GitHub repository.
When using v0.166.1 I have full access to the issue tracker of my repository, something I heavily use to keep track of things (and to keep things transparent). But as soon as I upgrade to a later version (this includes the recently released 0.170.0) I can no longer see the full overview of these issues.
v0.166.1 shows me existing milestones, the assigned (and non-assigned) issues and all other current issues (including those not assigned to me). But as soon as I upgrade the only thing I get to see are some issues mentioned under "Recent issues", everything else is gone (including mention of any milestones).
I made sure to log out & back in on all accounts (I use both my GitHub & Microsoft account), but that doesn't change anything. I also see no obvious errors or warnings in the plugin output window.
Activity
alexr00 commentedon Oct 15, 2026
I'm not able to reproduce this. Can you share the output from GitHub Pull Request?
ShelLuser commentedon Oct 15, 2026
Thanks for your response, I did some further investigations and came to these conclusions:
The previous situation (v0.166.1)
So, this is what things look like when I'm using the older version of the extension; everything works normally as expected.
The current situation (v0.170.1)
And this is what happens when I upgrade to the latest version of the plugin. As you can see I still keep access to the recent issues, but everything else (including any milestones) are fully gone.
My current theory
Based on your comment (thanks again) I tried to test the situation in a cleaner environment. I cloned my repository to a new folder, then opened VS Code after which everything works as expected; also using the current version(s) of the extension.
However... my project uses 2 Git remotes: the repo as it's hosted on GitHub (this is the primary, called
origin), but I'm also relying on a private server; so I have a second remote calledzefiriswhich I access over SSH.And as soon as I add this second remote to my temporary testing environment I immediately run into the problem I mentioned above. As such my conclusion that the cause of the glitch seems to be related to the handling of my 2nd remote. Even though the extension should be able to ignore it (as far as I understand) because I specifically set the
remotesconfig option to "origin" and "upstream"; so it should completely ignore zefiris as far as I can tell.