Talk about Pull Requests

This is a good first issue. @thephilgray Let's talk about making Pull Requests (PRs). We should not making direct changes to master.

Formatting

Let's try to be thorough with our PRs. The goal is for the other person to be able to review what we do as quickly as possible.

Keep branches small. If you want to add a feature, don't add a feature and then some styling for example.
Give instructions on how to test.
Give a brief description of the feature added, bug fixed, etc.
Include pictures. This especially for visual stuff like CSS changes/additions.
Give code blocks. A lot of changes made are minor. Give a code block explaining the crux of the PR.
Mark if it's blocker. We need to prioritize reviewing branches that block progress on other issues.

Please reply with questions and ideas about PRs. I want to know what you think. What do you think our standards should be?