Skip to content

♻️ refactor(worktree): run git via -C to target repository#39

Merged
samzong merged 1 commit intomainfrom
fix-root-path-error-3
Jan 9, 2026
Merged

♻️ refactor(worktree): run git via -C to target repository#39
samzong merged 1 commit intomainfrom
fix-root-path-error-3

Conversation

@samzong
Copy link
Owner

@samzong samzong commented Jan 9, 2026

No description provided.

Signed-off-by: samzong <samzong.lu@gmail.com>
@gemini-code-assist
Copy link

Summary of Changes

Hello @samzong, 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 refactors the underlying Git command execution within the worktree management system. By consistently applying the git -C <repository_directory> argument, it ensures that all Git operations are precisely targeted at the correct repository, which improves the reliability and robustness of worktree operations. Additionally, the mechanism for discovering the bare repository root has been refined to handle more edge cases, contributing to a more resilient system.

Highlights

  • Refactored Git Command Execution: All Git commands related to worktree management (add, remove, prune, branch deletion, fetch) now consistently utilize the -C flag to explicitly target the correct repository directory, ensuring operations are performed in the intended context.
  • Improved Bare Repository Root Detection: The FindBareRoot function has been enhanced to correctly identify the repository's root directory even when the starting path is directly within a .bare directory.
  • New Test Case for Root Detection: A new test, TestFindBareRoot_FromBareDir, was added to validate the improved logic for finding the bare repository root.

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

Copy link

@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 refactors the way git commands are executed by using the -C flag to explicitly target the repository directory. This is a good improvement for robustness and clarity. The changes are applied consistently across prune, add, remove, and dup functionalities for worktrees. Additionally, the FindBareRoot function is improved to handle cases where the starting directory is the .bare directory itself, and this change is properly covered by a new test case. I have one minor suggestion to further improve code clarity by reducing a small amount of duplication. Overall, this is a solid refactoring.

Comment on lines 317 to 325
var args []string
branchExistsFlag, _ := c.branchExists(name)
if branchExistsFlag {
// Branch exists: create worktree from existing branch
args = []string{"worktree", "add", targetPath, name}
args = []string{"-C", repoDir, "worktree", "add", targetPath, name}
} else {
// Branch does not exist: create new branch
args = []string{"worktree", "add", "-b", name, targetPath, baseBranch}
args = []string{"-C", repoDir, "worktree", "add", "-b", name, targetPath, baseBranch}
}

Choose a reason for hiding this comment

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

medium

To reduce code duplication and improve readability, you can initialize the args slice with the common command parts and then append the branch-specific arguments inside the if/else block.

Suggested change
var args []string
branchExistsFlag, _ := c.branchExists(name)
if branchExistsFlag {
// Branch exists: create worktree from existing branch
args = []string{"worktree", "add", targetPath, name}
args = []string{"-C", repoDir, "worktree", "add", targetPath, name}
} else {
// Branch does not exist: create new branch
args = []string{"worktree", "add", "-b", name, targetPath, baseBranch}
args = []string{"-C", repoDir, "worktree", "add", "-b", name, targetPath, baseBranch}
}
branchExistsFlag, _ := c.branchExists(name)
args := []string{"-C", repoDir, "worktree", "add"}
if branchExistsFlag {
// Branch exists: create worktree from existing branch
args = append(args, targetPath, name)
} else {
// Branch does not exist: create new branch
args = append(args, "-b", name, targetPath, baseBranch)
}

@samzong samzong merged commit cd9f72e into main Jan 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant