+1, seems like a great idea to me. I had no idea there was some kind of specification for this. We chose something ad-hoc with a similar intention in AsterixDB.
On Wed, Jul 2, 2025 at 1:44 PM Yicong Huang <[email protected]> wrote: > > Hi all, > > Currently, our PR titles and commit messages are written primarily for > human readability. While that’s useful, adopting a more structured format > would allow us to automate downstream processes more easily — such as > generating changelogs, release notes, and filtering commits by type. > > To that end, I propose we adopt the Conventional Commits specification > <https://www.conventionalcommits.org/en/v1.0.0/>. Specifically, this would > apply to: > > > 1. > > *Commit messages* > 2. > > *Pull request titles* (which become the squashed commit message in the > master branch) > > This format adds semantic meaning to commits using a simple prefix like > feat:, fix:, or docs: — for example: > > - feat(operator): add a new join operator > > - fix(ui): resolve layout issue > > - chore(ci): update GitHub Actions matrix > > > Unless there are objections, I’d like to move forward with adopting and > enforcing this convention going forward. > > > Best regards, > Yicong Huang
