🐛 Fix authentication token retrieval in GraphQL service#26
Merged
Conversation
java3east
requested review from
a team and
Friedinger
and removed request for
a team
Friedinger
approved these changes
Sep 6, 2025
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
2 participants
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.
Description:
This PR fixes an issue in the GraphQLService class where authentication was not correctly applied, causing GitHub GraphQL requests to fail. With this fix, the service now properly includes the authentication token in requests, ensuring that all GraphQL queries and mutations are executed successfully.
Changes:
Corrected the authentication handling in GraphQLService.
Verified that GitHub GraphQL queries now return expected results.
Impact:
GitHub GraphQL requests are now correctly authenticated.
Downstream features depending on GraphQL queries should function as expected.