Skip to content

fix(patch): cherry-pick 173376b to release/v0.33.0-preview.1-pr-21157 to patch version v0.33.0-preview.1 and create version 0.33.0-preview.2#21300

Merged
galz10 merged 1 commit intorelease/v0.33.0-preview.1-pr-21157from
hotfix/v0.33.0-preview.1/0.33.0-preview.2/preview/cherry-pick-173376b/pr-21157
Mar 5, 2026
Merged

fix(patch): cherry-pick 173376b to release/v0.33.0-preview.1-pr-21157 to patch version v0.33.0-preview.1 and create version 0.33.0-preview.2#21300
galz10 merged 1 commit intorelease/v0.33.0-preview.1-pr-21157from
hotfix/v0.33.0-preview.1/0.33.0-preview.2/preview/cherry-pick-173376b/pr-21157

Conversation

@gemini-cli-robot
Copy link
Collaborator

This PR automatically cherry-picks commit 173376b to patch version v0.33.0-preview.1 in the preview release to create version 0.33.0-preview.2.

@gemini-code-assist
Copy link
Contributor

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 automates the creation of a new patch release for the preview version by integrating a specific commit. The core change involves updating a read-only policy configuration to grant permissions for two additional tools, ensuring their functionality within the defined constraints.

Highlights

  • Patch Release Automation: This pull request automatically cherry-picks commit 173376ba67600499bccd57dbc79b94f7706c9db3 to create a new patch version v0.33.0-preview.2 from the existing v0.33.0-preview.1.
  • Policy Configuration Update: New rules have been added to the read-only.toml policy file, explicitly allowing the codebase_investigator and cli_help tools to operate within this policy.
Changelog
  • packages/core/src/policy/policies/read-only.toml
    • Added new policy rules to allow codebase_investigator and cli_help tools.
Activity
  • This pull request was automatically generated by gemini-cli-robot to perform a cherry-pick operation for a patch release.
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.

Copy link
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 cherry-picks a commit to add a new policy rule to read-only.toml. The new rule allows the codebase_investigator and cli_help tools, which is appropriate as they are read-only in nature. The change is functionally correct. I have kept the comment regarding a formatting issue as it does not contradict any provided rules.

Note: Security Review has been skipped due to the limited scope of the PR.

[[rule]]
toolName = ["codebase_investigator", "cli_help"]
decision = "allow"
priority = 50 No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

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

high

The file is missing a newline at the end. It's a common convention and often enforced by formatters like Prettier to end files with a newline character. Please add one for consistency and to adhere to the project's formatting standards.

References
  1. The repository style guide specifies the use of Prettier for formatting (line 19). Prettier's default behavior is to ensure a single newline at the end of files, which this change omits. (link)

@gemini-cli gemini-cli bot added the status/need-issue Pull requests that need to have an associated issue. label Mar 5, 2026
@github-actions
Copy link

github-actions bot commented Mar 5, 2026

Size Change: -2 B (0%)

Total Size: 25.9 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 25.4 MB -2 B (0%)
./bundle/node_modules/@google/gemini-cli-devtools/dist/client/main.js 221 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/_client-assets.js 227 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/index.js 11.5 kB 0 B
./bundle/node_modules/@google/gemini-cli-devtools/dist/src/types.js 132 B 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B
./bundle/sandbox-macos-strict-open.sb 4.82 kB 0 B
./bundle/sandbox-macos-strict-proxied.sb 5.02 kB 0 B

compressed-size-action

@galz10 galz10 merged commit 59702f9 into release/v0.33.0-preview.1-pr-21157 Mar 5, 2026
28 checks passed
@galz10 galz10 deleted the hotfix/v0.33.0-preview.1/0.33.0-preview.2/preview/cherry-pick-173376b/pr-21157 branch March 5, 2026 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

status/need-issue Pull requests that need to have an associated issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants