So you've worked on a new feature (or a patch). And it's time to commit your work. What do you put in the commit message? How much detail do you really need?
And more importantly...what should you NEVER put in a commit message?
====
Don't forget to order your copy of Learning Spring Boot 3.0 3rd Edition today at https://springbootlearning.com/book!
====
RESOURCES: 👇
Spring Data code Formatting tools - https://github.com/spring-projects/spring-data-build/tree/main/etc/ide
Order your copy of Learning Spring Boot 3.0 3rd Edition today at https://springbootlearning.com/book!
Spring Boot Learning Podcast: https://springbootlearning.com/podcast
This channel's github repositories: https://trnq.st/sfd5
GET MORE: 🎉
Get a FREE tech ebook at https://springbootlearning.com/join
Follow me on Twitter: https://twitter.com/springbootlearn
GRAB A MUG FOR YOUR COFFEE ☕ (and a t-shirt): https://store.springbootlearning.com/
STUFF I LIKE TO USE: 😍
Studio gear: https://springbootlearning.com/kit
Laptop stand: https://springbootlearning.com/twelvesouth-curve
Motorized standing desk: https://springbootlearning.com/desk
Music: https://springbootlearning.com/epidemicsound
Recut (pre-editing): https://springbootlearning.com/recut
Thumbnail Testing: https://springbootlearning.com/thumbnailtest
Best place to run Spring Boot apps: https://tanzu.vmware.com/
DISCLOSURE: All opinions stated here are mine and do not necessarily reflect those of the Spring team nor of my employer. Any usage of "Spring", "Spring Boot", "Spring Framework", "VMware", "Pivotal", or anything else is completely unaffiliated with its owners. From time to time, I may post affiliate links for products I enjoy using. They don't cost you anything extra, and I may get a small commission.
© 2023 Greg L. Turnquist, All Rights Reserved