Skip to content
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

Option to support conventional commits #9

Closed
hongbo-miao opened this issue Mar 9, 2023 · 6 comments · Fixed by #10
Closed

Option to support conventional commits #9

hongbo-miao opened this issue Mar 9, 2023 · 6 comments · Fixed by #10

Comments

@hongbo-miao
Copy link

It would be great to support conventional commits format! Thanks! 😃
Something like commitgpt provided, can be an extra -c.

@appleboy
Copy link
Owner

appleboy commented Mar 9, 2023

See the PR #10

@appleboy
Copy link
Owner

appleboy commented Mar 9, 2023

conventional commits as a default function to add prefixes to the commit title.

appleboy added a commit that referenced this issue Mar 9, 2023
- Add support for conventional commits
- Add a new template for conventional commits
- Update the `prompt.go` file to include the new template
- Remove the `ignoreLists` field from the `Command` struct in `git.go`

fix #9
@appleboy
Copy link
Owner

appleboy commented Mar 9, 2023

https://github.com/appleboy/CodeGPT/releases/tag/v0.0.5

@hongbo-miao
Copy link
Author

hongbo-miao commented Mar 9, 2023

Thanks @appleboy ! However, I am not sure how to use it.

I only got message like this

➜ codegpt commit
Summarize the commit message use gpt-3.5-turbo model
We are trying to summarize a git diff
We are trying to summarize a title for pull request
================Commit Summary====================

Update prefectTag version in my-values.yaml file

- Update the `prefectTag` to version `2.8.5-python3.11` in `my-values.yaml` file.

==================================================
Write the commit message to .git/COMMIT_EDITMSG file

In this case, the commit message is Update prefectTag version in my-values.yaml file, currently I copy this message manually and then commit by git commit -m "Update prefectTag version in my-values.yaml file".

I was expecting a conventional commit style like chore(prefect): update prefectTag version in my-values.yaml file got generated if it supports by default.

Could you clarify how to generate conventional commit or update the readme? Thanks! 😃

@hongbo-miao
Copy link
Author

hongbo-miao commented Mar 9, 2023

Ah you published a new version, I see, thanks!
Then I guess need somehow update the readme to install latest version by default, right now the readme is fixed on old version 0.0.4

image

@appleboy
Copy link
Owner

appleboy commented Mar 9, 2023

Update document in 4343ed4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants