I love this. I bet you are a kickass developer. And, insofar as you are not a kickass developer, you are moving with great velocity toward that endpoint.
Writing is thinking. Taking time to craft your thoughts about a commit, and to express them clearly, is a gift to others, and also like an intense workout for you.
Now I want to check out the repo and read these commit messages :)
Now I want to check out the repo and read these commit messages :)
I was talking about this Github comment, not about a commit message :)
Fortunately, I don't take so long for commit messages, lol
If I can't find a good commit message within seconds (max 1 minute probably), then my commit is not a good commit!
But the pull request description also took some time, I think. But that was definitely worth it. Makes life easier for @k00b to review and for me since I have written down my approach and can use it as a reference now. The TODOs are also nice to keep track of my progress.
@bitcoinplebdev inspired me to write better PR descriptions like this one :)
reply