-
Notifications
You must be signed in to change notification settings - Fork 42
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
Promote Git Commit Msg conventions #107
base: main
Are you sure you want to change the base?
Conversation
git commit -m "chore: Add empty doc."</pre> | ||
<p> | ||
Tip: consider using the conventions <q><a href="http://karma-runner.github.io/1.0/dev/git-commit-msg.html">Git Commit Msg</a></q>. | ||
</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM, but maybe link to repos that have already adopted these conventions for W3C spec work.
(also, if we want to promote it, documenting them is necessary but clearly not sufficient :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM, but maybe link to repos that have already adopted these conventions for W3C spec work.
done.
(also, if we want to promote it, documenting them is necessary but clearly not sufficient :)
Agreed. The first step is to update the documentation so that we can point to it while promoting. I'm currently promoting the pull request :)
#98 is likely related |
We should stir our community towards using Git Commit Msg conventions. This would facilitate the review of commit logs. Proposal is to start with Get Commit Msg.