di-sukharev / di-sukharev/opencommit
[Feature]: Add Caching to avoid reruns
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Cache exact matches to avoid having to generate the text again.
This happens often when a pre-commit hook stops the commit. If there's more than one file in the commit, the unchanged files should have the commit message ready since it was generated before.
Suggested Solution
A simple string matching database (Langchain has that implementation) should work.
Maybe a Sqlite database that gets cleaned up after 24 hours or something like that.
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
No files, tests, or implementation entry points are named. Start by tracing the pre-commit hook's message-generation flow and determine how exact matches should be reused across unchanged files; done means reruns are avoided and cached data follows the agreed cleanup policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, sqlite
- Domain
- cli, performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100