When it comes to version control, Git is a very effective tool. However, like any other tool you have... Tagged with git, developer, productivity.

hantian pang

GitHub

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn how to write effective Git commit messages following the Conventional Commits specification. Understand the different types of commit messages, the optional use of scope, and the recommended formatting for concise and informative messages.

Are You Writing Your Git Commit Messages Properly?

Thanks for sharing ✨✨
It is essential to write good and clear commit for better understanding of what have changed. The standard format does it so well. I’ll try to write my next commits better 🔥.

No. Absolutely not. I hate seeing commit messages that start “feat:” etc. It’s like a pet peeve. I don’t know where that nonsense started, but it’s terrible advice. Those “tags” are just noise and should not be used.
<s>I don’t remember where I read it, but I know I trusted the source enough…</s> (Found it) <a href="https://cbea.ms/git-commit/" target="_blank" rel="noopener nofollow">I read on this blog</a>, the “right way” is to write the message so it completes the sentence “If applied, this commit will…” Once you understand what a commit is and how it works, this way makes a lot more sense and makes things a lot easier to follow than trying to parse “feat:” “fix:” “docs:” noise.