di-sukharev / di-sukharev/opencommit
[Feature]: make top_p and temperature parameters configurable
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
I believe that if we set top_p or temperature to something more chill like 0.5~0.7 models would better perform instead of sticking to the few shot examples we provide as examples before every commit generated.
Suggested Solution
oco config set OCO_TOP_P=0.5 or oco config set OCO_TEMPERATURE=0.5
Alternatives
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing oco config set handling and the code that supplies model parameters during commit generation. Check how current configuration values are stored and read. Done means OCO_TOP_P and OCO_TEMPERATURE can be configured through the suggested command and affect generated commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100