Skip to content

fix: adress pr comments task not respecting worktrees#484

Merged
Shironex merged 1 commit intov0.11.0rcfrom
feature/v0.11.0rc-1768405788678-28bn
Jan 14, 2026
Merged

fix: adress pr comments task not respecting worktrees#484
Shironex merged 1 commit intov0.11.0rcfrom
feature/v0.11.0rc-1768405788678-28bn

Conversation

@Shironex
Copy link
Copy Markdown
Collaborator

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jan 14, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @Shironex, 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 an issue where automated tasks for handling PR comments and resolving conflicts were not properly respecting Git worktrees. By explicitly setting the workMode to custom and linking it to the current worktree's branch, the system will now correctly execute these tasks within the intended worktree environment, enhancing the reliability and accuracy of these operations.

Highlights

  • Worktree Awareness Fix: Introduced workMode: 'custom' to task configurations for both PR feedback and conflict resolution. This ensures that these tasks correctly identify and operate within the context of the active Git worktree's branch.

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

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.

@Shironex Shironex added the Bug Something isn't working label Jan 14, 2026
Copy link
Copy Markdown
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

The changes correctly introduce the workMode: 'custom' property when creating features for addressing PR comments and resolving conflicts. This ensures that these tasks are properly associated with the specific worktree's branch, aligning with the intended functionality. The implementation is consistent with how workMode is handled in the handleAddFeature function, correctly deriving the branchName for feature creation.

@Shironex Shironex merged commit 63e0ffa into v0.11.0rc Jan 14, 2026
6 of 7 checks passed
@Shironex Shironex deleted the feature/v0.11.0rc-1768405788678-28bn branch January 14, 2026 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant