Skip to content

fix(scripts): correct typo in split-repo migration post-process script - #18929

Open
Jah-yee wants to merge 1 commit into
googleapis:mainfrom
Jah-yee:fix/pacakges-typo
Open

Jah-yee wants to merge 1 commit into
googleapis:mainfrom
Jah-yee:fix/pacakges-typo

Conversation

@Jah-yee

@Jah-yee Jah-yee commented Oct 30, 2026

Copy link
Copy Markdown

Summary

Fixes a typo in the split-repo migration helper script.

Change

scripts/split_repo_migration/multiple-library.post-process.sh:78 prints the following banner when the script post-processes a repository that contains multiple packages:

Post-processing multiple pacakges
  PATH_MONOREPO:         /path/to/repo

The word pacakges is misspelled; it should be packages. The correction is made in the heredoc that generates this output:

-Post-processing multiple pacakges
+Post-processing multiple packages

This script lives under scripts/split_repo_migration/ and is maintained by hand rather than being emitted by the generator, so the fix can be applied directly.

Scope

  • One file changed: scripts/split_repo_migration/multiple-library.post-process.sh
  • One line changed (1 insertion, 1 deletion)
  • No behavioural change: only the text of the printed banner is affected
  • The generated client libraries under packages/ are untouched

Verification

  • git diff --check passes with no whitespace errors
  • The script still parses as valid shell (bash -n clean)
  • The heredoc delimiters and the surrounding PATH_MONOREPO expansion are unchanged, so the printed output format stays identical apart from the corrected spelling

@Jah-yee
Jah-yee requested a review from a team as a code owner October 30, 2026 19:50

@gemini-code-assist gemini-code-assist Bot left a comment

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.

Code Review

This pull request fixes a typo in the post-processing script, correcting 'pacakges' to 'packages'. There are no review comments, and I have no feedback to provide.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant