Dev Home GitHub Extension: More GitHub instance type support needed & more information needed to help people sign-in correctly #813
Labels
Area-Account-Sign-In
Related to authenticating with extensions
Issue-Feature
New feature or request
Resolution-Duplicate
This issue or pull request already exists
Suggested new feature or improvement
(1) Need to be able to sign into GitHub EMU and GitHub Enterprise Server and get data into DevHome.
(2) Developers need to be able to see repository information organized by GitHub instance type & accounts.
(3) It needs to be very clear what username is being used to sign-in as the current approach merely opens the default browser and whatever GitHub account was last active there will be what is signed into. If a sign-in has already occurred in recent past, the browser seems to skip the page that tells you what instance and account you are signing into. It merely says "you are signed in and can go back to DevHome". This occurs even if you have already signed out on DevHome side. This leads to a confusing user experience. It would be helpful to have more information related to this BOTH before clicking "sign-in" and after "sign-in" is complete. Perhaps a "how to sign-in to multiple accounts or instances" helper information at a link?
Scenario
It is common for people in an enterprise to have multiple GitHub accounts for different instances of GitHub or even different users for the same instance in less common situations. Instances can include GitHub public, GitHub EMU, GitHub Server, etc. In some cases, the same username might be used across different instances but different login URLs.
Given developers work occurs across these instances, all should be supported and it should be clear where each repository issue or PR notification comes from.
Additional details
Currently (2023-05-24), it is possible to sign-in to GitHub EMU successfully on DevHome but no data shows up. Ideally, there would be a message about GitHub EMU not being supported after sign-in.
The text was updated successfully, but these errors were encountered: