di-sukharev / di-sukharev/opencommit
[Feature]: set the prompt input as a value in an rc file
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
I'd love to see the prompt input be a config file that could be dropped in my home directory.
This would allow me to customize the prompt for my needs without a custom build.
Suggested Solution
See git-aicommit and the usage of $HOME/.gitcommitrc that can be configured.
I think that's useful to allow prompt updates or tweaks.
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 locating the CLI configuration handling and the code that assembles the prompt input; the issue does not name specific files or tests. Compare the proposed $HOME/.gitcommitrc approach with the existing configuration behavior. Done means prompt values can be customized through an rc file without a custom build, with coverage for loading and applying the configured value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100