Skip to content

fix(git): set vscode as default mergetool, remove fugitive#58

Merged
chicham merged 1 commit intomainfrom
fix/git-mergetool-config
Feb 21, 2026
Merged

fix(git): set vscode as default mergetool, remove fugitive#58
chicham merged 1 commit intomainfrom
fix/git-mergetool-config

Conversation

@chicham
Copy link
Copy Markdown
Collaborator

@chicham chicham commented Feb 21, 2026

Summary

  • merge.tool = mergiraf was incorrect: mergiraf is a merge driver (automatic), not a mergetool (interactive). Setting it as merge.tool caused unexpected fallback behaviour.
  • Set merge.tool = vscode for manual conflict resolution when mergiraf cannot auto-resolve.
  • Remove [mergetool "fugitive"] — redundant (duplicates nvim via a vim plugin).
  • Remove fugmerge alias.

The [merge "mergiraf"] driver configuration is unchanged.

Closes #45

mergiraf is a merge driver (automatic), not a mergetool (interactive).
Setting merge.tool = mergiraf was incorrect and caused unexpected fallback
behaviour. Set merge.tool = vscode for manual conflict resolution.

Also removes the redundant fugitive mergetool (a vim plugin that duplicates
nvim functionality) and its fugmerge alias.

Closes #45
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @chicham, 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 refines the Git configuration to ensure proper handling of merge conflicts. It corrects an erroneous merge.tool setting by replacing the merge driver mergiraf with vscode for interactive conflict resolution. Additionally, it streamlines the configuration by removing redundant fugitive merge tool definitions and its associated alias.

Highlights

  • Git Merge Tool Correction: The merge.tool setting was incorrectly configured to mergiraf, which is a merge driver, not an interactive merge tool. This has been corrected.
  • Default Merge Tool Set to VS Code: The default interactive merge tool (merge.tool) is now set to vscode to handle conflicts that mergiraf cannot auto-resolve.
  • Fugitive Merge Tool Removal: The [mergetool "fugitive"] configuration was removed as it was redundant, duplicating functionality already provided by Neovim.
  • Fugmerge Alias Removed: The fugmerge Git alias, which pointed to the removed fugitive merge tool, has also been removed.

🧠 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
  • dot_gitconfig.tmpl
    • Changed the default merge.tool from mergiraf to vscode in the [merge] section.
    • Removed the entire [mergetool "fugitive"] configuration block.
    • Deleted the fugmerge alias from the [alias] section.
Activity
  • No human activity has occurred on this pull request yet.
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
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

This pull request correctly fixes a misconfiguration in the git settings by changing the default merge tool from mergiraf to vscode, as mergiraf is a merge driver and not an interactive mergetool. The changes also include removing the redundant fugitive mergetool and its associated alias, which cleans up the configuration. The changes are logical, well-explained, and improve the correctness and maintainability of the git configuration. I have no further suggestions.

@chicham chicham merged commit bdae882 into main Feb 21, 2026
@chicham chicham deleted the fix/git-mergetool-config branch February 21, 2026 10:59
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.

Fix gitconfig: Incorrect merge.tool setting and redundant mergetool configs

1 participant