Add option to disable OpenAI/generate commit message

[rognstad]

Please add an option to disable the "generate commit message" feature and others that send information to OpenAI. Many companies have strict policies regarding the release of IP that this feature potentially violates. Thanks!

[eamodio]

Can you provide more details on why a "disable" option is useful? The AI features are not automatic -- they need to be manually triggered through an explicit user action, and then you are prompted to allow the sending of the required information to OpenAI.

[rognstad]

If the option is visible, people are going to be tempted to click on it. The resulting popup has a fair bit of text, and OpenAI isn't mentioned until the fifth line. Plenty of people unwisely reflexively hit enter or proceed through confirmation dialogs. Given an example organization where no one is supposed to send code to AI models, it would be much preferable to disable that option in all of their workspaces than rely on every individual to never make this particular mistake

[eamodio]

Gotcha -- thanks for the additional context.

[griffi-gh]

i hate AI (especially if "cloud"-based) and hate OpenAI even more.
I want an option that hides all AI features, like "hide all Gitlens+ Features" option.

[JeanTerblanche]

+1 for a setting for this - and also the Explain this Commit panel below.

A workspace setting will at least provide a mechanism for organizations who wish to limit data sharing with 3rd parties.

In general, having the ability to disable Experimental or GitLens+ features would also be very useful.

[griffi-gh]

@JeanTerblanche :

In general, having the ability to disable Experimental or GitLens+ features would also be very useful.

There's already an option to hide all GL+ features (you can enable only if you don't have the subscription, and after your trial ends. Otherwise (if you have full access to gl+ features), it has no effect)

[DanielPower]

I certainly won't be subscribing to GitLens if it's going to force these options to be visible.

Many companies (mine included) do not allow the use of unauthorized AI tools that involve uploading of source code for analysis. And that's a very reasonable stance.

You're taking up valuable visual real estate in my editor, for a feature I cannot and do not want to use. And increasing the probability that developers are going to break company security policy.

[griffi-gh]

I certainly won't be subscribing to GitLens if it's going to force these options to be visible.

the features are free for local and public repos.

you can hide them if you want, just wait for your 14 day trial to expire and then open the command pallete -> Hide GitLens+ features

[michalbielecki]

I already have GitLens+ features hidden but still see "Explain (AI)" panel in GitLens inspect view

[eamodio]

@michalbielecki that's because it's not a restricted/paid feature.

[michalbielecki]

I was referring to the comment above claiming that disabling paid features would hide AI related stuff

[DanielPower]

I certainly won't be subscribing to GitLens if it's going to force these options to be visible.

the features are free for local and public repos.

you can hide them if you want, just wait for your 14 day trial to expire and then open the command pallete -> Hide GitLens+ features

I recognize that I can hide them with the option you mentioned on a free plan. However that option does not work on a paid account. Thus my statement that I would not subscribe.

The company has decided to make it so that paying for a subscription makes it impossible to hide this functionality. Thus for me a paid subscription is objectively worse than the free plan. Paying for a subscription would not be a consideration for me until that is addressed.

[CyprusSocialite]

Can you provide more details on why a "disable" option is useful? The AI features are not automatic -- they need to be manually triggered through an explicit user action, and then you are prompted to allow the sending of the required information to OpenAI.

For screen real estate at the very least. "Explain (AI)" and Autolinks clutter the commit details panel whether you use those features or not - the latter even when completely disabled in settings!

[eamodio]

@DanielPower The AI features have nothing to do with free/paid plans at all -- they aren't gated and aren't pro features. This request to hide them is completely valid, but again is completely separate from Pro etc

[eamodio]

@douira The setting name is gitlens.ai.experimental.generateCommitMessage.enabled (note the gitlens. prefix).

[eamodio]

@douira If you were aware of it, why did you post suggesting the setting didn't exist or didn't work?

I added that setting when I added support to contribute to the new button in the SCM input box (41cae89), explicitly for the reason that it highly visible (whereas the existing feature was not) and something that users could definitely want to disable.

vscode-gitlens/package.json

Lines 3080 to 3086 in 8dd2ac6

	"gitlens.ai.experimental.generateCommitMessage.enabled": {
	"type": "boolean",
	"default": true,
	"markdownDescription": "Specifies whether to enable GitLens' experimental, AI-powered, on-demand commit message generation",
	"scope": "window",
	"order": 1
	},

[zigomir]

@douira The setting name is gitlens.ai.experimental.generateCommitMessage.enabled (note the gitlens. prefix).

this doesn't work for me

My main issue with this AI feature is that I used to be able to type my commit message, hit tab and then hit enter and be done with it. Now after hitting a tab this Generate commit message kicks in and rewrites my commit message – very annoying 😔

[eamodio]

@zigomir My guess is that you have Copilot or another extension installed that is also contributing to that button.

[zigomir]

@eamodio oh, you're right, I'm sorry for the noise 😊

[kpostekk]

@douira The setting name is gitlens.ai.experimental.generateCommitMessage.enabled (note the gitlens. prefix).

this doesn't work for me

My main issue with this AI feature is that I used to be able to type my commit message, hit tab and then hit enter and be done with it. Now after hitting a tab this Generate commit message kicks in and rewrites my commit message – very annoying 😔

My solution: microsoft/vscode-copilot-release#359 (comment)

[SampsonCrowley]

Can you provide more details on why a "disable" option is useful? The AI features are not automatic -- they need to be manually triggered through an explicit user action, and then you are prompted to allow the sending of the required information to OpenAI.

it's also extremely annoying when the button covers part of what I'm typing for a feature I'l never use or be allowed to

[SampsonCrowley]

[d13]

it's also extremely annoying when the button covers part of what I'm typing

@SampsonCrowley - its a bug with VS Code (#3034)

[eamodio]

You can turn off the GitLens contribution to that button by setting gitlens.ai.experimental.generateCommitMessage.enabled to false

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.