Skip to content

Dry run of step 6 of migration process#16608

Draft
jskeet wants to merge 5 commits intogoogleapis:mainfrom
jskeet:dry-run
Draft

Dry run of step 6 of migration process#16608
jskeet wants to merge 5 commits intogoogleapis:mainfrom
jskeet:dry-run

Conversation

@jskeet
Copy link
Copy Markdown
Contributor

@jskeet jskeet commented Apr 10, 2026

No description provided.

@jskeet jskeet added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Apr 10, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 migrates the repository to the new librarian system by adding a comprehensive librarian.yaml configuration and updating existing configuration and state files to support google-area120-tables and google-cloud-config. Key feedback includes a critical correction for the tag_format which currently uses invalid characters for Git tags, and recommendations to capitalize API descriptions in both the YAML and JSON metadata files for consistency and professional formatting.

- docs/README.rst
default:
output: packages
tag_format: '{name}: v{version}'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The tag_format contains a colon and a space ({name}: v{version}), both of which are invalid characters for Git reference names (tags). This will cause the release process to fail when attempting to create a tag. Consider using a standard format like {name}-v{version}.

  tag_format: '{name}-v{version}'

version: 0.14.0
apis:
- path: google/area120/tables/v1alpha1
description_override: provides programmatic methods to the Area 120 Tables API.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The description in description_override should start with a capital letter for consistency with other library entries (e.g., line 72) and to ensure professional formatting in generated documentation.

    description_override: Provides programmatic methods to the Area 120 Tables API.

"product_documentation": "https://area120.google.com",
"release_level": "preview",
"repo": "googleapis/google-cloud-python"
"api_description": "provides programmatic methods to the Area 120 Tables API.",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The api_description should start with a capital letter. This field is typically used as the package description on PyPI and in documentation, so proper capitalization is important for clarity and professionalism.

Suggested change
"api_description": "provides programmatic methods to the Area 120 Tables API.",
"api_description": "Provides programmatic methods to the Area 120 Tables API.",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant