Have your duties ever included reviewing code commits before they are merged into a codebase? If so, you know that the description provided with the change set can make a huge difference in the ease or difficulty of evaluating the change. But if you're anything like me, once it comes time to actually write such a change description yourself, you sometimes draw a blank. When you've been elbows-deep in code, it can be hard to gain the needed perspective to write a useful summary for other developers' consumption.
What if, instead of confronting a blank slate, you had a little extra guidance in writing up your pull requests? In today's episode, guest chef Andy Croll will demonstrate how using a pull request template can improve a team's communication around code reviews. Enjoy!