We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.0.11
21.6.2
10.2.4
Mac
When using ollama as the AI engine, it mistakenly considers the example git diff of server.ts in its output.
server.ts
Example:
Changed port variable case and added support for configurable port in server.ts
Often times, it is the ONLY change it displays. It also ignores formatting, emoji, etc.
(In addition, the mistral LLM is hard-coded for some reason, when it should be possible to try others)
mistral
Output should look like it does with using OpenAI and not consider the sample input git diff.
See "What happened."
OC_OLLAMA_MODEL
No response
The text was updated successfully, but these errors were encountered:
will be releasing next version this weekend, lets see if this is healed, thank you @digitalstudium <3
Sorry, something went wrong.
done, 3.0.12 is out, please npm i -g opencommit
npm i -g opencommit
No branches or pull requests
Opencommit Version
3.0.11
Node Version
21.6.2
NPM Version
10.2.4
What OS are you seeing the problem on?
Mac
What happened?
When using ollama as the AI engine, it mistakenly considers the example git diff of
server.ts
in its output.Example:
Often times, it is the ONLY change it displays. It also ignores formatting, emoji, etc.
(In addition, the
mistral
LLM is hard-coded for some reason, when it should be possible to try others)Expected Behavior
Output should look like it does with using OpenAI and not consider the sample input git diff.
Current Behavior
See "What happened."
Possible Solution
OC_OLLAMA_MODEL
variable rather than hard-codedmistral
LLM.Steps to Reproduce
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: