-
Notifications
You must be signed in to change notification settings - Fork 1.6k
chore: librarian onboard pull request: 20260204T073039Z (google-cloud-apiregistry) #15522
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @chalmerlowe, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request automates the onboarding of the Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request onboards the new google-cloud-apiregistry client library. The changes are mostly boilerplate generated by the Librarian CLI. I've found a few areas for improvement: the API description in .repo-metadata.json is empty, and the logging examples in the README files use placeholders. I've provided suggestions to address these points.
|
|
||
| .. code-block:: console | ||
|
|
||
| export GOOGLE_SDK_PYTHON_LOGGING_SCOPE=google.cloud.library_v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for flagging the potentially missed library name replacement.
Having said that, the current text is as it should be. Because this is generic text used for several hundred libraries, the template uses the term library_v1 to avoid the additional complexity of updating all the names for each module.
Please remember this.
I am resolving all comments in this PR related to library_v1.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for clarifying that the use of library_v1 is intentional due to the generic nature of the template across multiple libraries. I understand the design choice and will take this into account for future reviews.
Updates api_description
|
The |
PR created by the Librarian CLI to onboard a new Cloud Client Library.
BEGIN_COMMIT
feat: onboard a new library
PiperOrigin-RevId: 848064295
Library-IDs: google-cloud-apiregistry
END_COMMIT
Librarian Version: v0.8.0
Language Image: us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:d3ae275c61acca91e1398581edfb9119c521b4e93f9ebb00ecbd4e87b71648f5