It would be nice if there is an option to use <a href="https://www.conventionalcommits

<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="16

Closed via <a class="issue-link js-issue-link" data-error-text="Failed to load title"

Add support for conventional commits about aicommits HOT 10 CLOSED

nutlope commented on May 30, 2024 77

Add support for conventional commits

from aicommits.

Comments (10)

Nutlope commented on May 30, 2024 28

This is a top priority feature that's currently in the README. We'll try to prioritize it and release it soon!

from aicommits.

guanguans commented on May 30, 2024 6

Share my repository(https://github.com/guanguans/ai-commit) written in PHP.
Support to generate multiple conventional messages for us to choose.

Here is the prompt I am using:

Here is the output of the `git diff`:
<diff>
Here are some best practices for writing commit messages:
- Write clear, concise, and descriptive messages that explain the changes made in the commit.
- Use the present tense and active voice in the message, for example, "Fix bug" instead of "Fixed bug."
- Use the imperative mood, which gives the message a sense of command, e.g. "Add feature" instead of "Added feature"
- Limit the subject line to 72 characters or less.
- Capitalize the subject line.
- Do not end the subject line with a period.
- Limit the body of the message to 256 characters or less.
- Use a blank line between the subject and the body of the message.
- Use the body of the message to provide additional context or explain the reasoning behind the changes.
- Avoid using general terms like "update" or "change" in the subject line, be specific about what was updated or changed.
- Explain, What was done at a glance in the subject line, and provide additional context in the body of the message.
- Why the change was necessary in the body of the message.
- The details about what was done in the body of the message.
- Any useful details concerning the change in the body of the message.
- Use a hyphen (-) for the bullet points in the body of the message.
Write <num> commit messages that accurately summarizes the changes made in the given `git diff` output, following the best practices listed above and the conventional commit format.
Please provide a response in the form of a valid JSON object and do not include "Output:", "Response:" or anything similar to those two before it, in the following format:
[
    {
        "id": 1,
        "subject": "<type>(<scope>): <subject>",
        "body": "<BODY (bullet points)>"
    },
    ...
    {
        "id": n,
        "subject": "<type>(<scope>): <subject>",
        "body": "<BODY (bullet points)>"
    }
]

from aicommits.

warengonzaga commented on May 30, 2024 3

This is must be added as a feature.

from aicommits.

ThijSlim commented on May 30, 2024 3

#177

from aicommits.

kwiss commented on May 30, 2024 2

conventional commits is a must have +1 let's go for the prompt addition of @thijslimmen

from aicommits.

andreacavagna01 commented on May 30, 2024 1

from aicommits.

vanarok commented on May 30, 2024 1

Such a simple function and such a long implementation.

from aicommits.

ThijSlim commented on May 30, 2024

I created the following PR to enable conventional commits as configuration:
#160

from aicommits.

Braunson commented on May 30, 2024

Even the functionality to specify a "prefix" to prefix the commit message would be a quick one.. i.e. aitcommit -p "chore:"

Edit: Looks like that is already available via -t or --type

from aicommits.

privatenumber commented on May 30, 2024

Closed via #177

from aicommits.

Add support for conventional commits about aicommits HOT 10 CLOSED

Comments (10)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent