Give the ability to skip or ignore SSO on an organization's public repo

[Aymendje]

My personal github account is linked to some of my organization repos.
To sign in with my organization privileges, I need to be connected through VPN (or their SSO will reject me)
But if I am connected on my personal github and I want to see a public repo owned by my organization, it directly prompts me the SSO login page and I cannot skip it. The only way to access the page is through incognito / disconnect from my Github account.

Here is an example to be clear :

aymendje (my personal github account) is linked to the Microsoft organization (that requires 2FA / SSO)
When I try to access a page like https://github.com/microsoft/vscode/releases/, it forces me to sign in

But since I am on my personal device / not connected to VPN / Corpnet, my 2FA gets rejected and I am stuck in the Microsoft's SSO Error page (you are not authorized)

Ideally, we would have a button "view this page outside my organization" or simply "skip" alongside the "continue" button, and view the page without signing in to the organization.

I guess that I should have 2 github accounts, a professional one, and a work one, but its so much simpler to use only one and leverage the organizations instead !

[Ashesh3]

How is this still a thing in 2024? I have the exact same issue. I do not want to escalate my privileges by using single sign-on for a public repo and instead want to interact with it with my personal account. It's really troublesome to open an incognito window just to access a public repo.

[thesofakillers]

bump

[mark-wiemer]

Wild that this is still happening. I'm just opening these pages in InPrivate tabs for now, a terrible workaround :(

[mark-wiemer]

I've since disconnected my personal GitHub from my work one, always fun to have two accounts for the same purpose :(

[sethupavan12]

bump.
It's been almost 3 years with no update or ETA for a fix.

[agg23]

Expressing my frustration with this as well. It seems like a number of Microsoft employees in particular are being hit with this, given the responses in this thread.