Repository navigation
Save a copy to GitHub: OAuth authorization fails after the code callback (Microsoft Edge) #6199
Description
Describe the current behavior
Saving a copy of a notebook to GitHub fails at the OAuth authorization step. GitHub login and consent both succeed, but Colab never completes the handshake and no repository is created.
Observed in the browser's own history (Edge), 2026-11-04 01:03–01:08 local time — the OAuth round trip does complete on GitHub's side, four times in a row:
01:03:33 https://github.com/login/oauth/authorize?scope=public_repo,gist&client_id=5036cf6d81e65aaa6340&state=qF9fE3_O...
01:05:40 https://colab.research.google.com/auth/github?code=7303ba382d4f7df775b4&iss=https%3A%2F%2Fgithub.com%2Flogin%2Foauth&state=qF9fE3_O...
01:05:58 https://github.com/login/oauth/authorize?scope=public_repo,gist&client_id=5036cf6d81e65aaa6340&state=zrOND3na...
01:05:58 https://colab.research.google.com/auth/github?code=8061b877ed727c407dc4&iss=https%3A%2F%2Fgithub.com%2Flogin%2Foauth&state=zrOND3na...
01:07:48 https://github.com/login/oauth/authorize?scope=public_repo,gist&client_id=5036cf6d81e65aaa6340&state=4Y2B1Qnk6...
01:07:48 https://colab.research.google.com/auth/github?code=cfda54d660920c28f998&iss=https%3A%2F%2Fgithub.com%2Flogin%2Foauth&state=4Y2B1Qnk6...
01:07:58 https://github.com/login/oauth/authorize?scope=public_repo,gist&client_id=5036cf6d81e65aaa6340&state=ubzRCU2Zo...
01:07:58 https://colab.research.google.com/auth/github?code=4d9a8e5bab42cc035379&iss=https%3A%2F%2Fgithub.com%2Flogin%2Foauth&state=ubzRCU2Zo...
01:07:58 https://colab.research.google.com/auth/github
The authorization code is delivered back to colab.research.google.com/auth/github every time, so the failure happens after GitHub grants access — during Colab's code-for-token exchange — rather than during the GitHub consent screen. The Colab UI reports an authorization failure and no repository appears.
Describe the expected behavior
Choosing "File > Save a copy in GitHub" should complete the OAuth handshake and commit the notebook to the chosen repository.
What web browser you are using
Microsoft Edge on Windows (build 10.0.26200 x64). Chrome is installed on the same machine but has never been used for Colab, so I could not yet test the browser difference.
Additional context
- This appears to be the same failure as Unable to save to colab notebooks to github #6158 ("Unexpected response from GitHub. Please try again."), where another reporter observed the same behaviour in Edge while Chrome worked. I am adding browser-history evidence to help narrow the cause.
- Attempted so far, all with the same result: repeated authorization attempts; signing in to GitHub in a separate tab; granting consent to
scope=public_repo,gist; retrying with the target repository pre-created. The GitHub account is a personal account with no organization membership, so organization SSO / third-party-app restrictions should not apply. - The OAuth
client_id=5036cf6d81e65aaa6340requestsscope=public_repo,gist. - Because the failure is after the code callback, I suspect the code-for-token exchange or the subsequent repository-creation call is what fails, rather than the consent step itself. I did not capture the exact on-screen error string, so please treat the browser history above as the primary evidence rather than the error text.
Link to a minimal, public, self-contained notebook that reproduces this issue:
- Share the file using your GitHub account using File > Save a copy as a GitHub Gist.
- or Share Drive notebooks using the Share button then 'Get Shareable Link'.
Activity