refactor: drop serde_yaml by migrating to toml by jpoehnelt · Pull Request #657 · googleworkspace/cli
Summary of Changes
Hello, 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 migrates the project's internal AI skill registry from YAML to TOML. The primary motivation for this change is to eliminate the unmaintained serde_yaml dependency, which was flagged during supply chain audits, and replace it with the actively maintained toml crate. This change includes updating the registry files and the corresponding parsing logic in the CLI tool.
Highlights
- Dependency Management: Removed the unmaintained
serde_yamldependency and addedtomlto improve supply chain security. - Registry Migration: Migrated internal AI skill registry files (personas and recipes) from YAML to TOML format.
- Codebase Update: Updated the
generate_skillsmodule to parse TOML files instead of YAML, ensuring compatibility with the new registry format.
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.
Footnotes
-
Review the Generative AI Prohibited Use Policy, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩