-
Notifications
You must be signed in to change notification settings - Fork 9.9k
fix: Settings in Folder trust hook #7343
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @shrutip90, 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 addresses a bug related to folder trust settings within the CLI. It refines the logic for overriding the approval mode to default, ensuring it only occurs when a folder is explicitly marked as untrusted. Additionally, it updates the useFolderTrust hook to align with a revised structure for passing security-related settings, specifically for folder trust, to the isWorkspaceTrusted utility function.
Highlights
- Folder Trust Logic Refinement: Modified the condition for forcing approval mode to default in
config.tsfrom!trustedFoldertotrustedFolder === false. This ensures that the approval mode is only overridden when the folder is explicitly untrusted, preventing unintended overrides when the trust status is undefined or null. - Settings Structure Update: Updated the
useFolderTrusthook to pass folder trust settings within a nestedsecurity.folderTrustobject structure to theisWorkspaceTrustedfunction. This change aligns the settings consumption with a potentially updated or standardizedSettingsinterface.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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
-
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. β©
There was a problem hiding this 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 introduces two important fixes for the folder trust mechanism. The first correctly adjusts the logic for overriding the approval mode, ensuring it only happens when a folder is explicitly marked as untrusted. The second fix addresses a bug in the useFolderTrust hook where the workspace was always considered trusted. My review includes one suggestion to refine the implementation of the fix in the hook for better clarity and maintainability.
Code Coverage Summary
CLI Package - Full Text ReportCore Package - Full Text ReportFor detailed HTML reports, please see the 'coverage-reports-22.x-ubuntu-latest' artifact from the main CI run. |
jacob314
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be nice to follow up with a test to make sure this doesn't regress
(cherry picked from commit 1fc1c2b)
TLDR
Dive Deeper
Reviewer Test Plan
Testing Matrix
Linked issues / bugs