fix(gitcommit): remove caret from log range

[jinzhongjia]

Verify .git directory and remove deps/mini.nvim before cloning.

[gemini-code-assist]

Summary of Changes

Hello @jinzhongjia, 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 two distinct but important areas: refining how Git commit logs are generated and improving the reliability of dependency installation. It corrects the git log range specification within the gitcommit extension by removing an unnecessary caret, which ensures accurate commit history retrieval for release notes. Concurrently, it enhances the mini.nvim dependency installation process by adding a more thorough check for a valid Git repository and ensuring a clean re-clone if the existing dependency is found to be incomplete or corrupted.

Highlights

• Git Log Range Correction: The git log command used for generating release notes has been updated to remove the ^ character from its range specification, ensuring a more standard and potentially more inclusive commit range for history retrieval.
• Robust Dependency Cloning: The mise.toml configuration for installing mini.nvim now includes a more robust check for a valid .git directory within the dependency. If the .git directory is missing or invalid, the existing deps/mini.nvim directory is removed before attempting a fresh clone, preventing issues with corrupted or incomplete installations.

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

[gemini-code-assist]

Code Review

This pull request correctly fixes the git log range for release notes by removing the caret, which prevents the starting tag from being included in the log. It also improves the robustness of the test dependency installation script in mise.toml by ensuring a clean clone even if a partial or corrupted directory exists. I have one suggestion to further improve the robustness of the Windows script to align its error handling behavior with the Unix version.

[gemini-code-assist]

The use of -ErrorAction SilentlyContinue can mask failures. If Remove-Item fails for a reason other than the path not existing (e.g., permissions), the error is suppressed, and the script proceeds to git clone, which will then fail with a potentially confusing message. The Unix equivalent command uses &&, which correctly prevents git clone from running if the removal fails.

To make the Windows command more robust and align its behavior with the Unix command, it's better to first check if the directory exists before attempting removal and to use an error action that halts the script on failure.

Suggested change

	if (-not (Test-Path deps/mini.nvim/.git)) { Remove-Item -Recurse -Force deps/mini.nvim -ErrorAction SilentlyContinue; git clone --depth 1 https://github.com/echasnovski/mini.nvim deps/mini.nvim }
	if (-not (Test-Path deps/mini.nvim/.git)) { if (Test-Path deps/mini.nvim) { Remove-Item -Recurse -Force deps/mini.nvim -ErrorAction Stop }; git clone --depth 1 https://github.com/echasnovski/mini.nvim deps/mini.nvim }