How often have you found commit messages in your Git history to be uninformative? Or alternatively, wordy rambles that are slow to read β and may well not have the information you need anyway?
Headline + Bullet Points is an approach Iβve found to make Git commit messages informative and fast to write.
Continue reading β
Continuing last monthβs theme of searching Git history β here we look at how to find the source of changes, even after other people have worked on (or reformatted) the area in question.
The question: which commit actually introduced a given string into the file? Continue reading β
Working on many separate enhancements.. How to find which branch my changes to a particular file are on? And if a file was deleted, how can I find that?
Luckily, Git can help us! Continue reading β
From the Classic Programmer Paintings blog. Enjoy!

βOperations and Developers agreeing on Git workflowβ
Jacques-Louis David, 1796-1799, Oil on Canvas
(collaboration from @rpiaggio )
Insights into Java coding, OO design & architecture