microsoft / vscode-copilot-release

Feedback on GitHub Copilot Chat UX in Visual Studio Code.
https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat
Creative Commons Attribution 4.0 International
295 stars 28 forks source link

How to disable semantic commit messages? #1212

Open grooveshaker opened 1 month ago

grooveshaker commented 1 month ago

I made an update just a few days ago and now when I use the “Generate commit message with Copilot” feature, I get the messages chore: and feat: in the commit message. I am not a fan of this feature, but is there any way to prevent these messages from being output? I have looked in past issues and looked in the settings but have not found a solution. Thank you in advance.

My VSCode version is 1.89.1 GitHub Copilot version is v1.191.0

jira-zz commented 1 month ago

I'am experiencing the same issue. Not sure if it is a bug or feature, but I don't like the change.

digitarald commented 1 month ago

Can you confirm that other commits in the repo you are working in are not using semantic commit formatting?

grooveshaker commented 1 month ago

Sure. There was a commit message generated using Copilot in the version just prior to the drafting of this issue. Unfortunately, this repository is private, so the commits cannot be shared, but when these commits were soft reset and re-committed identically, the commit messages certainly did not contain semantic commit messages. Am I right in saying that if I don't want to include semantic commit messages in a commit message, I must first manually edit the commit message, but at some point the semantic commit message will no longer be included? Does this mean that Copilot is generating commit messages based on previous commit messages in addition to the staged changes?

grooveshaker commented 3 weeks ago

As it turns out, past commit messages do not seem to be affected.

When I tried it on my unpublished old repository, it outputs a commit message that contains those keywords, even though I had never written a commit message containing chore or fix before. However, I am now wondering if it is inevitable because it is an LLM product, since chore may not be included depending on the contents of the commit.

However, considering that these commit messages were not included at all before, I have to assume that there must have been some changes due to the version upgrade.