You're writing Git commit messages wrong
You're writing Git messages wrong Here are 2 ways to improve your Git commit messages: 1. Use imperative present tense Source: Git Documentation Your message should describe what applying the commit will do — not what you did.
You're writing Git messages wrong
Here are 2 ways to improve your Git commit messages:
1. Use imperative present tense
Source: Git Documentation
Your message should describe what applying the commit will do — not what you did.
Think of completing this sentence:
When merged, this commit will…
- Fix bug preventing users from subscribing
- Add validation for email addresses
- Update IDs to latest versions
In fact, we see the imperative mood throughout tech, e.g. in UI prompts like “Enter username” - learn more here .
2. Use Conventional Commits
Add prefixes to make Git history easier to scan
- feat → new feature
- fix → bug fix
- refactor → code change, no behaviour change
👇 Keep scrolling for a full list of conventional commits
FEATURED
Want to get the most out of ChatGPT?
ChatGPT is a superpower if you know how to use it correctly.
Discover how HubSpot's guide to AI can elevate both your productivity and creativity to get more things done.
Learn to automate tasks, enhance decision-making, and foster innovation with the power of AI.
Download the free guide
RESOURCES
CareerAddict's The Dose
Free Career Planning Worksheet — when you subscribe to The Dose for weekly insights on growing your career, increasing income, and working smarter. Join 20K+ pros.
CareerAddict's The Dose
Conventional Commits
A specification for adding human and machine readable meaning to commit messages
FEATURED
Tired of Hearing: "Figure out our AI strategy"? Join Workzone's live session and walk into your next vendor call as the toughest person in the room, armed with the four questions that cut through any pitch. June 25, 11 AM CT. Register now →
VISA-SPONSORED TECH JOBS
ML/AI Platform Engineer at Monzo Remote, UK
Data Scientist - AI Search & Ranking at trivago Hybrid, Germany
Senior Backend Engineer at Vinted Hybrid, Lithuania
View 200+ roles on The Stack Jobs →
What did you think of today's email? 🤔
Great 😃 | Good 🙂 | Could be better 😐
What a job seeker should do this week
- Save this advice, then open roles that already say visa sponsorship
- Ask on the first recruiter call whether they have filed from your country this year
- Browse <a href="/jobs/section/freshest-jobs">freshest jobs</a> and <a href="/jobs/section/english-first-jobs">English-first jobs</a>
Source: The Stack newsletter — <a href="https://www.trythestack.co/p/2-ways-to-improve-git-commit-messages">original issue</a>.
Frequently asked questions
What should job seekers take from this?
You're writing Git messages wrong Here are 2 ways to improve your Git commit messages: 1. Use imperative present tense Source: Git Documentation Your message should describe what applying the commit will do — not what you did.
What should I do after reading this?
Fix bug preventing users from subscribing
Does this apply if I need visa sponsorship in Europe?
Yes. Use it on roles that will file papers. Skip listings that only say international with no visa line.