# Pull Request and Commit Templates
## We've all seen this style PR
[example](https://github.com/MITLibraries/bento/pull/6)
Communication without context is hard. It makes the reviewer
have to think harder than necessary.
## This is better
[example](https://github.com/MITLibraries/bento/pull/268)
Context is given so the reviewer can more easily review the code.
## How?
[Official Docs](https://github.com/blog/2111-issue-and-pull-request-templates).
[Bento Example](https://raw.githubusercontent.com/MITLibraries/bento/master/.github/PULL_REQUEST_TEMPLATE.md)
## That's great for PR communication
### ...but PRs don't replace good commit mesages
[How to write good commit messages](https://robots.thoughtbot.com/better-commit-messages-with-a-gitmessage-template)
## My git commit template (`.gitmessage`)
```
What:
*
Why:
*
How:
*
# 50-character subject line
#
# 72-character wrapped longer description.
```