Capturing the reason why something was changed, why this approach was chosen, and possibly enumerating other approaches not taken (and why they weren't picked),

Capturing the reason why something was changed, why this approach was chosen, and possibly enumerating other approaches not taken (and why they weren't picked), are all gold to the Engineers of Tomorrow spelunking into some codebase. Summarizing a diff frequently doesn't add information that the diff itself already includes. Title or no title. I'm surprised we don't think about how to shout into the future more effectively. It might be ourselves that we're helping the most.