fix(auth): add default resolver to github auth provider - #153
Merged
Conversation
Signed-off-by: Jessica He <jhe@redhat.com>
jrichter1
approved these changes
Aug 24, 2026
gustavolira
added a commit
that referenced
this pull request
Aug 25, 2026
#153 landed and claimed 2.1.11, which this branch was holding. Third version collision on this PR — the Version Bump Check only compares against main, so it cannot see a claim another open PR is already sitting on, and the branch loses the race every time something else merges first. Nothing but bookkeeping: the changelog keeps our section on top with #153's 2.1.11 below it, and package.json moves to 2.1.12. 141 tests pass, yarn check clean, docs build clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a default
usernameMatchingUserEntityNamesign-in resolver to the GitHub auth profile to avoid this error:Sign-in fails with "... provider is not configured to support sign-in