starred/git-ai

Fork 0

mirror of https://github.com/git-ai-project/git-ai.git synced 2026-04-25 14:25:53 +03:00

[GH-ISSUE #424] Feature Request: Isolate Plugin Version from Native Git Command #157

New issue

Closed

opened 2026-03-02 04:12:23 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 04:12:23 +03:00

Owner

Originally created by @ShuboLiang on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/424

I suggest that the git --version command should strictly return the native Git version information. You could introduce a new command, such as git --full-version, to display both the Git version and the git-ai plugin version.
This is important because GUI Git tools (such as VS Code's Source Control) often invoke git --version to parse the string. If the output deviates from the standard format, it may cause parsing errors and lead to unexpected bugs. I am currently encountering this issue where pulling or pushing code in VS Code fails intermittently due to this version string conflict.

Originally created by @ShuboLiang on GitHub (Jan 30, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/424 I suggest that the git --version command should strictly return the native Git version information. You could introduce a new command, such as git --full-version, to display both the Git version and the git-ai plugin version. This is important because GUI Git tools (such as VS Code's Source Control) often invoke git --version to parse the string. If the output deviates from the standard format, it may cause parsing errors and lead to unexpected bugs. I am currently encountering this issue where pulling or pushing code in VS Code fails intermittently due to this version string conflict.

kerem closed this issue

2026-03-02 04:12:24 +03:00

kerem commented

2026-03-02 04:12:25 +03:00

Author

Owner

@ShuboLiang commented on GitHub (Jan 30, 2026):

I have another issue. When I configure the Git URL to point to git-ai in TortoiseGit, a black terminal window keeps popping up repeatedly whenever I execute certain commands. I'm not sure what's causing this. Could you please look into and fix this problem?

@ShuboLiang commented on GitHub (Jan 30, 2026): I have another issue. When I configure the Git URL to point to git-ai in TortoiseGit, a black terminal window keeps popping up repeatedly whenever I execute certain commands. I'm not sure what's causing this. Could you please look into and fix this problem?

kerem commented

2026-03-02 04:12:25 +03:00

Author

Owner

@acunniffe commented on GitHub (Feb 1, 2026):

Hey @ShuboLiang taking a look. What path did you try to point each to? In the .git-ai/bin folder you should see both a git (symlink) and git-ai (binary).

I believe both should work if you point at the symlink.

@acunniffe commented on GitHub (Feb 1, 2026): Hey @ShuboLiang taking a look. What path did you try to point each to? In the `.git-ai/bin` folder you should see both a git (symlink) and git-ai (binary). I believe both should work if you point at the symlink.

kerem commented

2026-03-02 04:12:26 +03:00

Author

Owner

@ShuboLiang commented on GitHub (Feb 1, 2026):

Hey @ShuboLiang taking a look. What path did you try to point each to? In the .git-ai/bin folder you should see both a git (symlink) and git-ai (binary).

I believe both should work if you point at the symlink.

Yes, I’ve configured it exactly as you described. @acunniffe

It works correctly in most cases, but I ran into an issue with one specific repository. The only difference I noticed is that its URL starts with http:// instead of https:// (though I’m not sure if this is actually causing the bug I mentioned). When I tried to pull from or push to this repository using VS Code's built-in source control tool, I encountered an error.

I traced the HTTP request and found— as shown in the attached screenshot—that the User-Agent header was split across two lines. This caused a 400 Bad Request error. Normally, the User-Agent header appears on a single line; splitting it over two lines can lead to parsing errors.

@ShuboLiang commented on GitHub (Feb 1, 2026): > Hey [@ShuboLiang](https://github.com/ShuboLiang) taking a look. What path did you try to point each to? In the `.git-ai/bin` folder you should see both a git (symlink) and git-ai (binary). > > I believe both should work if you point at the symlink. Yes, I’ve configured it exactly as you described. @acunniffe It works correctly in most cases, but I ran into an issue with one specific repository. The only difference I noticed is that its URL starts with http:// instead of https:// (though I’m not sure if this is actually causing the bug I mentioned). When I tried to pull from or push to this repository using VS Code's built-in source control tool, I encountered an error. I traced the HTTP request and found— as shown in the attached screenshot—that the User-Agent header was split across two lines. This caused a 400 Bad Request error. Normally, the User-Agent header appears on a single line; splitting it over two lines can lead to parsing errors. <img width="934" height="462" alt="Image" src="https://github.com/user-attachments/assets/7a7ff319-9ac9-4eba-8a67-aa7b1eb0eb6e" />

kerem commented

2026-03-02 04:12:26 +03:00

Author

Owner

@acunniffe commented on GitHub (Feb 1, 2026):

This was a short-lived regression. Can you upgrade to https://github.com/git-ai-project/git-ai/releases/tag/v1.0.40

git-ai upgrade should fix it

@acunniffe commented on GitHub (Feb 1, 2026): This was a short-lived regression. Can you upgrade to https://github.com/git-ai-project/git-ai/releases/tag/v1.0.40 `git-ai upgrade` should fix it

kerem commented

2026-03-02 04:12:26 +03:00

Author

Owner

@ShuboLiang commented on GitHub (Feb 1, 2026):

Thank you! It works.

@ShuboLiang commented on GitHub (Feb 1, 2026): Thank you! It works.

kerem referenced this issue

2026-03-02 04:13:13 +03:00

[PR #157] Move to virtual attestations for faster rewrite ops #295