-
Notifications
You must be signed in to change notification settings - Fork 1
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
gitmoji vs. conventional commits -- auto-generated changelog #121
Comments
I would be happy to do that. We might have to play around with setting up Is adding them to PRs also automated or do you have to do that manually? |
Some on our team don't use it for every commit. And I also think this is not sooooo helpful. So, I don't think it's a requirement. All our other repos have
It depends on when you create the PR. If you create it after making the first commit on a new branch, the PR title will have the commit message as title. But, to be honest, spending 1 min on making sure the PR title is well chosen and has an emoji that categorizes it well is well spent. I don't think automation is needed as it happens so rarely and should be done consciously. |
I see -- sure thing! We can switch to using this approach from the next release onwards :) |
Cool! :) |
Re: this change of the title in the corresponding PR
At Lamin, we're auto-creating the changelog and bucketing changes by UX (πΈ), bug fixes (π), new features (β¨) using the
gitmoji
pre-commit
hook (https://gitmoji.dev/).The idea is to get a friendly changelog without much effort, e.g., here: https://docs.lamin.ai/changelog/2024#db-0-76-16
So, if we add an emoji to the PR title, this here will be easy to read & re-organize: https://github.com/laminlabs/lamin-docs/blob/main/docs/changelog/soon/laminr.md
Similar to this: https://github.com/laminlabs/lamin-docs/blob/main/docs/changelog/soon/lamindb.md
Does this make sense -- can we do this also for
laminr
@lazappi @rcannood ? I know that most people use conventional commit instead of gitmoji but fastapi etc. are also following this alternative approach.The text was updated successfully, but these errors were encountered: