fix: Use auth_token rather than access_token - #23
Merged
Conversation
Collaborator
Author
|
Example failure from the test PR: https://github.com/google-gh-automation/workflows/actions/runs/27707684380/job/81960421576 |
jalseth
force-pushed
the
jalseth/auth-token
branch
from
June 17, 2026 18:38
12c291d to
43bfea3
Compare
access_token requires a GCP SA and we do not have those for this configuration.
This lets the CI run on PR before merging.
jalseth
force-pushed
the
jalseth/auth-token
branch
from
June 17, 2026 21:06
591b68c to
5f2b3a8
Compare
kevya-google
approved these changes
Jun 17, 2026
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.
access_token requires a GCP SA and we do not have those for this configuration.