You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
GitHubArea: what it touches
Bug FixesKind: in v2.1.273,
Bug FixesSection of the release
What
Importing a GitHub token now gives more actionable error messages:
Network errors are classified, and TLS-tunnel (ERR_PROXY_TUNNEL) failures now explain that the proxy refused the tunnel, via a new sslHint.
Generic network errors during token import/web-setup now surface the sslHint and/or which proxy environment-variable source is in effect.
Invalid-token (400) responses now parse the server's message and show it in the UI, appending guidance to add the repo scope.
Why
These changes turn generic, hard-to-diagnose network and token errors into specific messages that point at the actual cause, such as a proxy blocking the connection or a token missing a required scope.
