chore(internal/librariangen): change release-init to release-stage

[jskeet]

This makes the Go container comply with the Librarian changes in googleapis/librarian@e6d911d

Fixes googleapis/librarian#2785

[gemini-code-assist]

Summary of Changes

Hello @jskeet, I'm Gemini Code Assist¹! 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 updates the librariangen Go container to synchronize its release workflow command with the latest changes in the librarian tool. The primary release-init command has been refactored and renamed to release-stage, necessitating widespread changes across the codebase, documentation, and testing infrastructure to maintain compatibility and correct functionality.

Highlights

• Command Renaming: The release-init command within librariangen has been renamed to release-stage to align with recent changes in the upstream librarian tool.
• Codebase Updates: All internal references, function names, and file paths related to the release-init command have been updated to reflect the new release-stage naming convention across the Go source code and shell scripts.
• Documentation and Test Alignment: The README.md documentation, integration test scripts, and test data paths have been updated to use the release-stage command and associated file names, ensuring consistency and correct testing.

Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[jskeet]

Set to "do not merge" because we probably want to merge and start using #13290 quickly, but we need to coordinate using this change with automation.

[gemini-code-assist]

Code Review

This pull request primarily refactors the codebase by renaming release-init to release-stage to align with upstream changes in the Librarian tool. The changes are applied consistently across Go source files, test scripts, and documentation. I found one minor issue in the README.md where the updated librarian command was not correctly documented. Otherwise, the changes are thorough and look good.