chore: remove issue_tracker_override from librarian.yaml#16820
chore: remove issue_tracker_override from librarian.yaml#16820jskeet merged 7 commits intogoogleapis:mainfrom
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request performs a comprehensive cleanup and update of issue tracker configurations across numerous Google Cloud Python libraries. The changes involve removing redundant issue tracker links in librarian.yaml and package-specific .repo-metadata.json files, as well as migrating generic GitHub issue links to specific Google Issue Tracker components for several packages. I have no feedback to provide as there are no review comments to assess.
|
@parthea Quick ping while it's still within your working hours :) |
|
(Will resolve the conflicts in the morning.) |
jskeet
force-pushed
the
remove-issue-overrides-2
branch
from
27d0c8b to
4e85413
Compare
jskeet
force-pushed
the
remove-issue-overrides-2
branch
from
4e85413 to
5d6f1b7
Compare
(This will need another update in librarian's sdk.yaml)
jskeet
added
the
kokoro:force-run
yoshi-kokoro
removed
the
kokoro:force-run
The Kokoro jobs are broken (see googleapis#16512) so any changes in the crc32c package will fail.
|
googleapis/librarian#5671 will remove (eventually) the need for the override for compute/v1beta |
|
We should also be able to add an issue tracker for google-cloud-storage, but there's currently no entry in sdk.yaml at all for google/cloud/storage/v2, so we'll do that separately. |
|
I'll merge this if the Kokoro System Tests check goes green - core_deps_from_source is likely to time out again, and is unnecessary when no Python files have changed in the PR. |
3 participants
Issue tracker overrides are retained for:
This also skips generation for google-crc32c, as Kokoro tests are failing at the moment (#16512)
Towards googleapis/librarian#5465