Any way to make it compare previous changes? #268
Unanswered
johhansantana
asked this question in
Q&A
Replies: 1 comment
-
🤔 I think this is purely a model problem it seems. I've tested with llama 3.1 8b, 70b, 3b, Gemini, etc. The more advance the model is, the more "conscious" it is and focused more on the formatting. Best result so far is GPT-4o-mini |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm kind of assuming it doesn't check for previous changes and compares them? My assumption comes because if I update a file formatting only and don't change anything else, it will say that I created this and that when I haven't created anything, I've only formatted the code with prettier for example.
This is the prompt content I'm sending to claude-3-haiku:
Write a meaningful commit message in the conventional commit convention by trying to understand what was the benefits the code author wanted to add by his changes to codebase with this commit. I'll send you an output of 'git diff --staged' command, and you convert it into a commit message. Lines must not be longer than 74 characters. Use {locale} language to answer. End commit title with issue number if you can get it from the branch name: {branch} in parenthesis. Try to use line breaks, only after a dot, to help making the commit message easier to read.
{diff}
Beta Was this translation helpful? Give feedback.
All reactions