Writing a useful pull request description

Writing a technical explanation often reveals the bit I haven't understood. If I can't say why a change is needed without describing every implementation detail, I probably need another pass.

A useful pull request tells the reviewer what was wrong, what changes for the user and how it was checked. That takes a little time to write. It usually saves more time than it costs, including when I come back months later and have forgotten the whole thing.