Posted on
I forked tidythemes/blankslate to robertandrews/blankstrap.
I created new Issues for myself, for my own fork...
But, in VS Code, in the GitHub extension panel, I am instead seeing the Issues for the original blankslate...
Source Control Repositories shows...
Branch switcher shows...
Switching to another (ie. origin/master Remote) does not result in my Issues showing.
What must I do to get my own Issues visible?
For further actions, you may consider blocking this person and/or reporting abuse
Brett -
Shaik -
Sanjana Konte -
Christopher Cooper -
Once suspended, robertandrews will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, robertandrews will be able to comment and publish posts again.
Once unpublished, all posts by robertandrews will become hidden and only accessible to themselves.
If robertandrews is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Robert Andrews.
They can still re-publish the post if they are not suspended.
Thanks for keeping CodeNewbie Community 🌱 safe. Here is what you can do to flag robertandrews:
Unflagging robertandrews will restore default visibility to their posts.
Top comments (2)
The only way I can get them to display so far is by editing settings.json to add a new githubIssues.queries item:
Then, they show. But this, of course, means this is visible no matter what I open in VS Code.
Developer of the VS Code GitHub Issues extension suggests it may be a bug.