-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
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
📚 [Feature]: Proposal for User-customizable Prompts through Configuration Files #212
Comments
Do you have a code example for your proposed solution? |
@seho-dev I don't, but that's pretty straightforward. My intent is to gather feedback before doing this. |
Something like this maybe? (very rough)
|
Stale issue message |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
👋 Hi amazing OpenCommit maintainers and community! 🌟 First of all, a huge thanks to the code owners for the incredible work on OpenCommit. 🚀 I have a proposal that could make OpenCommit even more awesome. I'd love to hear your thoughts! 🧠
Currently, OpenCommit uses fixed prompts which are not customizable by users. Adding an ability for users to fine-tune the prompts would open up new possibilities and even facilitate community contributions for better prompts. 🛠️
#205
#191
#180 (Partially)
#135 (Partially)
#175
#155
#61
Suggested Solution
Let's allow OpenCommit to check for user-specific prompt files in
~/.opencommit/
(Or$HOME
). If present, it should use them, else fallback to the global defaults. This way, users can create and modify prompts as they like.~/.opencommit/
prompts exists, and load prompts from there if it does.Alternatives
Additional Context
This feature addresses many requests from the community about customizing commit message formats, prefixes, and ticket numbers. It’s a versatile solution that keeps everyone's preferences in mind. 🤗
💙 Looking forward to the community's feedback and insights! 🙏
The text was updated successfully, but these errors were encountered: