Feature: Prompt overrides

[nickradford]

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.

[nickradford]

Or is this already achievable using the prompt settings?

https://github.com/zurawiki/gptcommit/blob/c622fef4faf61c17ad47012fdcedaf1ec3513da9/src/summarize.rs#L34-L42

[zurawiki]

Hey @nickradford,

The features you describe should be available already. We could definitely benefit from more thought-out naming.

My team doesn't use conventional commits...

gptcommit config set output.conventional_commit false will disable the conventional commit globally.

gptcommit config set output.conventional_commit false --local will disable the conventional commit format for the current repo.

Something like gptcommit eject-prompt {PROMPT_NAME} which would write a file into the repo

If you want a repo-local override, run the command, gptcommit config set output.conventional_commit false --local
and a file will be added at .git/gptcommit.toml assuming .git is at the root of your git checkout. This toml file has all the prompts written there for you to edit.

gptcommit config list --save will write out all the prompts to your local home folder. From there, you can edit the TOML file at ~/.config/gptcommit/config.toml

If you find any better prompts, we'd love to add them back to this repo