chore: remove name_pretty_override from librarian.yaml#16812
chore: remove name_pretty_override from librarian.yaml#16812jskeet wants to merge 9 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 implements a large-scale update to product naming conventions across numerous client libraries, primarily by removing "Google" and "Google Cloud" prefixes from product names in metadata and documentation files. These changes are reflected in librarian configurations, repository metadata, and README files to ensure a more concise branding. I have no feedback to provide.
This isn't needed for handwritten libraries, and generated libraries should have values taken from sdk.yaml Towards googleapis/librarian#5463
jskeet
force-pushed
the
remove-name-pretty-override-2
branch
from
59fd8f8 to
59c3269
Compare
|
@ohmayr Please could you check the reason that Do we need to add google-cloud-python/.github/workflows/bigtable-conformance.yaml Lines 19 to 28 in 84f15e3 |
As of #16624, `django-google-spanner` presubmits are being triggered on every PR, regardless of whether `django-google-spanner` was changed. We should only trigger presubmit tests when there are changes to `django-google-spanner` or the action itself. See #16812 (comment)
|
Closing this PR so we can get everything else in first. |
2 participants
This isn't needed for handwritten libraries, and generated libraries should have values taken from sdk.yaml
Towards googleapis/librarian#5463