fix(cli): resolve drive letter casing mismatch in workspace trust check

[hiratara]

Why

This PR fixes a bug where users on Windows are incorrectly prompted to trust their workspace folder even if it is already trusted.

The issue was caused by strict string comparison (!==) used to filter the cwd from the IDE-provided workspace paths. On Windows, the IDE (VS Code) often provides paths with a lowercase drive letter (c:\), while the cwd might resolve with an uppercase letter (C:\). This mismatch causes the cwd to be erroneously added to includeDirectories a second time, triggering a redundant trust verification flow.

This is a regression introduced in PR #21380.

How

Replaced the strict string comparison with path.relative(). Since path.relative(a, b) === '' handles OS-specific path normalization and case-insensitivity natively, it reliably identifies when an IDE workspace folder matches the cwd, regardless of drive letter casing.

Fixes

Fixes #25085

[gemini-code-assist]

Summary of Changes

Hello, 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 addresses a regression in the workspace trust verification flow on Windows. By utilizing path-aware comparison methods instead of direct string matching, the CLI now correctly identifies workspace folders regardless of drive letter casing, preventing unnecessary user prompts.

Highlights

• Path Comparison Logic: Replaced strict string inequality checks with path.relative() to handle OS-specific path normalization.
• Windows Compatibility: Resolved an issue where drive letter casing mismatches on Windows caused redundant workspace trust prompts.

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

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. ↩

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[gemini-code-assist]

Code Review

This pull request updates the workspace folder path comparison in packages/cli/src/config/config.ts to use path.relative instead of a direct string comparison. This change ensures that path differences are handled safely across different operating systems by accounting for case insensitivity. I have no feedback to provide.