Repository navigation
chore: use CLOUD_JAVA_BOT_GITHUB_TOKEN in readme workflow - #14751
Merged
Merged
Conversation
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
jinseopkim0
marked this pull request as ready for review
October 23, 2026 15:12
whowes
approved these changes
Oct 23, 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
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.
Update
.github/workflows/readme.yamlto push theupdate-readmebranch directly and open the PR usingCLOUD_JAVA_BOT_GITHUB_TOKENinstead ofgoogleapis/code-suggesterwithYOSHI_CODE_BOT_TOKEN(which fails with a 500HttpErrorwhen syncing the fork).Note: This matches the existing PR creation pattern in
java-cloud-bom-update-readme-table.yamlandupdate_librarian_googleapis.yaml.b/577077828