fix: use custom fetch if defined in GitHub userInfo #12668
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes an issue in the GitHub provider where the function responsible for loading user info does not use the customFetch function when it is defined.
According to the official documentation Supporting Corporate Proxies, a custom fetch function can be defined to forward all authentication-related requests to a proxy. However, in this case, the request that retrieves user info was not routed through the proxy, causing the OAuth login flow to fail (if the environment where the app is deployed does not allow any requests to bypass the proxy).