Unintentional double commits

[Mojca Miklavec]

On 21 December 2016 at 22:38, Ivan Larionov wrote:
> One of the ways to avoid it is to review things you're going to merge. And
> one of the easiest ways to do it is to open a PR on github where you can
> clearly see which commits you're going to merge.

That doesn't necessarily help. The author can submit a pull request
which will get outdated by the time it gets committed – leading to
exactly the same problem at the end.

And clicking the button on the PR introduces the annoying wrong
committer email address.

Mojca