Prompt or config for auto generated commits

[eulke]

Is there any way to configure or give instructions on how i need the generated messages to be? I have a project with an automated changelog based on commits with conventional format, it would be nice to tell zed to use that format on auto generated commits

[nithinbull]

Yes It would be nice to have some amount of customisation to guide the model to generate messages with a specific format. Like say, "add the <branch_name | name | date> as header and number the commit messages"

[0x2CA]

Not so good now, because it's hardcoded

                let mut diff_text = diff.await??;

                const ONE_MB: usize = 1_000_000;
                if diff_text.len() > ONE_MB {
                    diff_text = diff_text.chars().take(ONE_MB).collect()
                }

                let subject = this.update(&mut cx, |this, cx| {
                    this.commit_editor.read(cx).text(cx).lines().next().map(ToOwned::to_owned).unwrap_or_default()
                })?;

                let text_empty = subject.trim().is_empty();

                let content = if text_empty {
                    format!("{PROMPT}\nHere are the changes in this commit:\n{diff_text}")
                } else {
                    format!("{PROMPT}\nHere is the user's subject line:\n{subject}\nHere are the changes in this commit:\n{diff_text}\n")
                };

                const PROMPT: &str = include_str!("commit_message_prompt.txt");

                let request = LanguageModelRequest {
                    messages: vec![LanguageModelRequestMessage {
                        role: Role::User,
                        content: vec![content.into()],
                        cache: false,
                    }],
                    tools: Vec::new(),
                    stop: Vec::new(),
                    temperature: None,
                };

commit_message_prompt.txt

You are an expert at writing Git commits. Your job is to write a short clear commit message that summarizes the changes.

If you can accurately express the change in just the subject line, don't include anything in the message body. Only use the body when it is providing *useful* information.

Don't repeat information from the subject line in the message body.

Only return the commit message in your response. Do not include any additional meta-commentary about the task. Do not include the raw diff output in the commit message.

Follow good Git style:

- Separate the subject from the body with a blank line
- Try to limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with any punctuation
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Keep the body short and concise (omit it entirely if not useful)

[nithinbull]

So the subject line is still preserved after the auto generation, that's convenient. But to have a new commit_message_prompt.txt prompt, should the editor be rebuilt?

[0x2CA]

So the subject line is still preserved after the auto generation, that's convenient. But to have a new commit_message_prompt.txt prompt, should the editor be rebuilt?

Yes, that's the way it is now.

[rprasquier-pass]

Being able to customize the prompt would allow some specific git commit message specification like gitmoji / conventional commits / etc.

[Lersoo]

This seems simple enough to update :

• add a setting in the git_panel_settings crate
• in the git_panel crate, replace the hard-coded PROMPT value with either the setting introduced beforehand, or the default value. something like :

const PROMPT: &str = GitPanelSettings::get_global(cx)
            .git_commit_prompt
            .unwrap_or(include_str!("commit_message_prompt.txt");

I'm not too sure about the syntax as I'm definitely not a Rust expert, but if that sounds like something you guys would like to see implemented, I'll be more than happy to try to work on a PR 🙂