Better Pull Request Emails
Since the new pull requests shipped just over a year ago, we have been sending out pretty sparse emails when someone created a new pull request on one of your…
Since the new pull requests shipped just over a year ago, we have been sending out pretty sparse emails when someone created a new pull request on one of your projects. You would get an email like this:
hey @jayne look at this real quick
--
Reply to this email directly or view it on GitHub:
https://github.com/jayne/ariel/pull/2
However, this really isn’t very much information, especially if the sender isn’t very verbose. So, we’ve expanded this with more of the pull request information – a list of the summary lines of the commits included, the files that were changed and links to the unified diff and patch versions. Your emails should now look something more like this:
hey @jayne look at this real quick
You can merge this Pull Request by running:
git pull https://github.com/malcom/ariel never-call-the-feds
Or you can view, comment on it, or merge it online at:
https://github.com/jayne/ariel/pull/2
-- Commit Summary --
* which is what happens when you call the feds
* hit the head with a wrench
* are they dead or just drugged
-- File Changes --
M neuro-imager.3d (15)
M st-lucys.txt (10)
A two-by-two.txt (2)
A hands-of-blue.txt (2)
D jayne.traitor (99)
-- Patch Links --
https://github.com/jayne/ariel/pull/2.patch
https://github.com/jayne/ariel/pull/2.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/jayne/ariel/pull/2
We’re continuing to improve the email experience on GitHub, so look for even more awesomeness going forward.
Written by
Related posts
The August 17 outage, and the work ahead
An update on the August 17 outage and the steps we’re taking to improve reliability.
Your guide to GitHub Universe 2026 is here: The schedule just launched!
The GitHub Universe session catalog is live. Explore interactive workshops, community talks, demos, and panels. Plus, register before August 19 to save $300.
GitHub availability report: July 2026
In July, we experienced eight incidents that resulted in degraded performance across GitHub services.