-
Notifications
You must be signed in to change notification settings - Fork 7
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardize Commit Message Format #83
Comments
Yes, I'm good with it. I've been using conventional commits, without scopes, for a bit now. I'm not sure we need them yet, but I've been using these CI jobs to catch unconventional commits in Bones:
I haven't bothered with merge queues or anything yet, though. I've just been squash-merging pull requests ( where I can modify the commit message before merging ), and pushing directly to mater for many of my changes, just for speed's sake. |
I am okay with the current situation; I just worry the repo will contain undesired formats or prefixes. Fortunately, we are on the same page. |
Closing this issue because it is currently non-actionable. |
Hi everyone, 馃憢馃徑
Should we start using a convention to standardize our commit messages? I propose we adopt the popular Angular Commit Message Format.
It's fine not to include the
scope
for now, but we should at least use the defined prefixes. This will prevent contributors from using arbitrary prefixes. Here are the prefixes we should use for each commit:What do you all think?
We should add this to our
CONTRIBUTING.md
documentation if we agree.The text was updated successfully, but these errors were encountered: