Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub extension: private repository does not show any issues #29558

Closed
bpasero opened this issue Jun 27, 2017 · 10 comments
Closed

GitHub extension: private repository does not show any issues #29558

bpasero opened this issue Jun 27, 2017 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Jun 27, 2017

Refs: #29507

Steps to Reproduce:

  1. open vscode-distro
  2. do not set any username in settings

=> no issues are showing but there are 4 open in that repository

@chrmarti
Copy link
Collaborator

Is this without credentials manager, I guess?

@chrmarti chrmarti added this to the June 2017 milestone Jun 27, 2017
@bpasero
Copy link
Member Author

bpasero commented Jun 27, 2017

This was actually on Windows with the GitHub for Desktop dialog popping up, so I think I was connected properly.

@chrmarti
Copy link
Collaborator

Is this one of the dialogs asking for permission to share credentials with the running application?

@bpasero
Copy link
Member Author

bpasero commented Jun 27, 2017

@chrmarti yeah exactly, and I get asked to enter my pin via SMS

@bpasero
Copy link
Member Author

bpasero commented Jun 27, 2017

@chrmarti btw everything works fine for the vscode repository (after I validated my pin via SMS).

@chrmarti
Copy link
Collaborator

@bpasero It might work as it should then. The distro repository does not show any open issues assigned to you, the view should just show a single entry saying it did not find any issues in this case.

@bpasero
Copy link
Member Author

bpasero commented Jun 27, 2017

@chrmarti yeah that is what I saw I think. I just thought that when I am not setting a user name in settings it would show issues from all users.

@chrmarti
Copy link
Collaborator

@bpasero It checks if the username it gets from the credentials manager is a valid username for that repository and then uses that. My hope was/is that most users will not need to configure anything to get useful results.

@bpasero
Copy link
Member Author

bpasero commented Jun 27, 2017

@chrmarti ok got it, then maybe we can close this issue.

@chrmarti
Copy link
Collaborator

Maybe the message when no issues are found could be improved by mentioning for which username the query ran. That would clarify that there might well be other issues.

@chrmarti chrmarti added the bug Issue identified by VS Code Team member as probable bug label Jun 27, 2017
@bpasero bpasero added the verified Verification succeeded label Jun 30, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
kieferrm pushed a commit to kieferrm/vscode-github-issues-prs that referenced this issue Apr 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

2 participants