This repo's commit messages are not good:
"A few more minor tweaks."
"A few more minor changes."
"Some extra file-list safety checks."
https://github.com/WayneD/rsync/commits/master
Those are the full commit messages. By way of comparison, here's what commit messages to git itself look like:
https://github.com/git/git/commit/198551ca54f6ff1c95c9357ccc...
https://github.com/git/git/commit/dee8a1455c8ad443ef59e0d5b7...
Each commit contains paragraphs of explanatory material. Jeff King's commit messages are "gold standards" to me, often well exceeding the size of the diff itself:
https://github.com/git/git/commit/aa0834a04e1d9d3ab81ecd4a4a...
https://github.com/git/git/commit/38f865c27d1f2560afb48efd2b...
https://github.com/git/git/search?q=author%3Apeff&type=commi...
Please folks, I beg of you, spend time writing your commit messages. You're not writing them for you today. You're writing them for others, including your future self. They should explain the commit: What is its goal? Why does it exist? Why was it written in this way? What other context does the developer need to understand this commit?
A PR description is not a substitute for a good commit message for multiple reasons:
1. If the PR is a single commit, then it's just the commit message and your job is probably done.
2. If there are multiple commits, then the PR description should summarize the goal of the aggregate of its commits.
3. The PR description is typically written hours or days after the commit(s). What was fresh in your head when you wrote that code is now stale and you will struggle to recall why you made a change in a particular way more than if you wrote it down fresh when you commit the change.
4. The PR description is not part of the repo's history. It requires access to a (typically propriety) platform to read.
So please, https://cbea.ms/git-commit/