Conversation
New context menu and inline button to open a terminal at any item's location. Terminal CWD resolves to the worktree directory for worktree/repository items, or the parent directory for workspace files. - Add "terminal" option to openBehavior setting with exhaustive switch - 4 customizable terminalName templates (favorites reuse non-favorite) - Inline $(terminal) button on non-favorite items - Leaf worktree/repository clicks now trigger openBehavior - QuickPick includes "Open in Terminal" / "Always Open in Terminal" - Prunable worktree guard (fs.existsSync check before createTerminal) - Fix resolveUri/resolveItemPath truthiness guard for GroupHeaderItem - 12 new tests covering all item types and error cases Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary of ChangesHello, 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 significantly enhances user interaction by introducing a versatile 'Open in Terminal' feature. Users can now quickly open a terminal at the location of any worktree, workspace file, or favorite item, either through context menus, an inline button, or by configuring it as the default click behavior. This streamlines workflows by providing direct command-line access from within the extension's tree view, making it easier to manage and navigate projects. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces the "Open in Terminal" command to the Git WorkGrove extension, allowing users to open a terminal at the location of worktrees, workspace files, or favorites. It also adds a "terminal" option to the openBehavior setting, enabling users to set the terminal as the default click action. The changes include modifications to the README, documentation, package.json, and several source files to integrate the new command and setting. The addition of a new test file ensures the functionality of the new command.
The never-typed default case already prevents compile-time misses; adding a runtime throw provides defense-in-depth if an invalid config value bypasses TypeScript types. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Summary
"terminal"toopenBehaviorsetting — users can set terminal as default click action$(terminal)button on non-favorite items for quick accessopenBehaviorterminalNametemplates (favorites reuse non-favorite templates)Test plan
dirnameof fileopenBehaviorto"terminal"→ clicking workspace file opens terminalopenBehavior781a193)🤖 Generated with Claude Code