"NPE is rough / solved one in main.java / per issue 15"
... is a legit commit message I may make. But why?
(This requires context for my non-dev friends so give me a minute to explain.)
A version control system is how nerds get work done. We use it daily and it has changed over the years. It used to be subversion or something else earlier but since 2005 the preferred choice has been something called git.
We like git. We have processes like gitflow and places like gitlab.com and github.com where we store our collaborative work.
We work in units. That unit is a commit. Think Ctrl+S to save your Word document. But with a twist.
The point of a commit is not just to save changes but to record why those changes were made. Thus, a common pattern is to include a message with your commit.
A commit, philosophically, should be small and atomic. It is a unit of work and there are bigger abstractions for larger tasks.
Therefore, a commit should be small. So should its message.
If you can't encapsulate a commit in a 5/7/5 syllable poem you have done too much at once. Let's keep our work clean and concise.
I'm not in a position to give advice but my philosophy is to keep things tight and focused.
However, I don't expect you to listen to me because I'm not the [force-pushed to main on a Friday] mentalist.