Do you use either semantic commit messages or conventional commits?
https://www.conventionalcommits.org/en/v1.0.0/
https://gist.github.com/joshbuchea/6f47e86d2510bce28f8e7f42ae84c716
Semantic Commit Messages
Semantic Commit Messages. GitHub Gist: instantly share code, notes, and snippets.Gist
- Always (16%, 16 votes)
- Often (22%, 22 votes)
- Rarely (23%, 23 votes)
- Never (37%, 37 votes)
This entry was edited (1 month ago)
Evan Prodromou reshared this.
This website is tracked using the Matomo analytics tool. If you do not want that your visits are logged in this way you can set a cookie to prevent Matomo / Piwik from tracking further visits of the site (opt-out).
Evan Prodromou
in reply to Evan Prodromou • • •Evan Prodromou
in reply to Evan Prodromou • • •Tommy Boy :verified:
in reply to Evan Prodromou • • •You just reminded me, I had this bookmarked to share with my nonprofit's interns and I never read it myself yet. So much to learn...
https://dev.to/otienorabin/are-you-writing-your-git-commit-messages-properly-54cl
Are You Writing Your Git Commit Messages Properly?
Rabin Otieno (DEV Community)Aljoscha Rittner (beandev)
in reply to Evan Prodromou • • •mthie®
in reply to Evan Prodromou • • •Evan Prodromou
in reply to mthie® • • •penryu
in reply to Evan Prodromou • • •Eric G.
in reply to Evan Prodromou • • •Bill Ricker
in reply to Evan Prodromou • • •naturzukunft
in reply to Evan Prodromou • • •Hippo 🍉
in reply to Evan Prodromou • • •I vaguely knew such things were there (especially when I see a lot of people adding `feat:` to the beginning of a message) but I've never bothered to investigate further
I do put effort into making sure my commit messages are descriptive (even in the title); in fact I've often realised during this process that maybe some changes don't belong in the same commit. But if you asked me to describe them I'd guess my messages were more "fun, literary vibes" than "formal, structured" 🤪
ms. liz
in reply to Evan Prodromou • • •ch0ccyra1n :she_her::neocat_floof_cute:
in reply to Evan Prodromou • • •Dan Jones 🥥🌴
in reply to Evan Prodromou • • •I use emoji commits with the gitmoji cli.
@evan@cosocial.ca
GitHub - carloscuesta/gitmoji: An emoji guide for your commit messages. 😜
GitHubEvan Prodromou
in reply to Evan Prodromou • • •Emelia 👸🏻
in reply to Evan Prodromou • • •used to use them both heavily, and conventional branching and more, but ultimately I've decided the benefits weren't actually worth it.
I rather do manual releases, and I now often prefer merge commits over rebase merges. The format can be a burden to other developers too!
I've even contributed to that tooling before! @stevendotjs can attest to that!
Olivier Mehani
in reply to Evan Prodromou • • •I do if the project needs it. Mainly for #changelog http://keepachangelog.com/ generation and automatic #semanticVersionning/#semanticRelease https://semantic-release.gitbook.io/semantic-release, but also for many-contributors projects.
I find it helps structure the commit history, too (avid user of interactive-rebase-before-merge here) so each commit is a meaningful set of changes, rather than a baby-uncertain bath+kitchen sink water [pause here, and picture in your mind].
I do this structuring even without semantic commits, but they make the approach explicit.
README | semantic-release
semantic-release.gitbook.ioDuncan Lock
in reply to Evan Prodromou • • •