> Handy pointers to all the branches you merged, in case you ever need them The one thing that GitHub does when it generates the merge commit (which it does ev

> Handy pointers to all the branches you merged, in case you ever need them The one thing that GitHub does when it generates the merge commit (which it does even for fast-forward merges) is that it adds a link to the PR associated with that commit. It's a handy way to go back to the PR and see the review of the branch before it was merged. For projects that use the email patch workflow like the Linux kernel or git itself, the merge commit message contains the branch name which can be used to find the mailing list discussion. In the git project, you can find the "what's cooking" emails to find the branch name and references to the message-id of the patch series cover letter.