-
Notifications
You must be signed in to change notification settings - Fork 77
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: Prompt overrides #157
Comments
Or is this already achievable using the prompt settings? Lines 34 to 42 in c622fef
|
Hey @nickradford, The features you describe should be available already. We could definitely benefit from more thought-out naming.
If you want a repo-local override, run the command,
If you find any better prompts, we'd love to add them back to this repo |
Is your feature request related to a problem? Please describe.
My team doesn't use conventional commits, so overriding the title or other prompts would be nice to have.
Describe the solution you'd like
Something like
gptcommit eject-prompt {PROMPT_NAME}
which would write a file into the repo (.gptcommit/prompts/{PROMPT_NAME}.tera
) with the default contents of that prompt, allowing a user to customize it.Describe alternatives you've considered
This could be on a per-repo basis, or they could be stored in the
~/.config/gptcommit
directory, even both with a chain of precendence (default -> dotfiles -> repo)Additional context
This would allow users to customize their prompts to be better tailored to their workflow, voice, or company requirements.
The text was updated successfully, but these errors were encountered: