Commit message on previous change

[mehha]

Sometimes it gives commit message based on previous change. I need to manually delete previous commit message and then generate again.

[Blarc]

Hey @mehha,

this seems a bit odd, since the plugin only looks at the diff of the current staged changes. It only adds the changes of the previous commit, if you checked the amend checkbox (#230).

[mehha]

Salvestamine.2025-01-13.113304.mp4

recorded screen. as you can see need to manually remove old message

[Blarc]

@mehha Huh, I'll have to test it myself. Maybe you can check the prompt that is sent in the settings of the prompt. There is a prompt preview text field, which should show the current diff that is sent.

[Blarc]

Does this also happen if you first push the first commit and then generate the commit message for the second?

[mehha]

@mehha Huh, I'll have to test it myself. Maybe you can check the prompt that is sent in the settings of the prompt. There is a prompt preview text field, which should show the current diff that is sent.

how I see this?

[mehha]

Does this also happen if you first push the first commit and then generate the commit message for the second?

yes

[Blarc]

@mehha Huh, I'll have to test it myself. Maybe you can check the prompt that is sent in the settings of the prompt. There is a prompt preview text field, which should show the current diff that is sent.

how I see this?

Edit the prompt:

[esafak]

Edit the prompt to what?

[Blarc]

Edit the prompt to what?

Edit the prompt to see the current diff that is sent in the preview text field.

[Blarc]

I've had it happened once to me, but I can't repeat it. Has anyone figure out what triggers this behaviour?

[Blarc]

Salvestamine.2025-01-13.113304.mp4
recorded screen. as you can see need to manually remove old message

Giving it another thought, this might occur if you use hint in your prompt, which adds the commit message in the box to the prompt.

[MarJose123]

I've had it happened once to me, but I can't repeat it. Has anyone figure out what triggers this behaviour?

I've encountered this issue by doing multiple commits. I noticed that there is a cache or something, as it generates the commit message based on the previous diff.

Can you try this to replicate:

1. Edit two files, e.g., filename_1, filename_2.
2. On the commit modal, select only filename_1 for generating the commit message. Once the commit message has been generated, commit that file, then
3. Generate again a commit message, but for filename_2, check the commit message.
4. Make sure the interval for doing this is not above 5 seconds for generating the commit message for filename_1 and filename_2.