We get at least one of those a day and they are user error, spam or something. Definitely a useful feature for popular open source projects.
Thus a shed load of commits to try and resolve the difference.
Hopefully this new behaviour does fix the problem. On the other hand, I have a feeling it might alienate potential contributors who just aren't that familiar with git yet and could instead do with some guidance (ie how to use the correct branch to base changes on).
I guess we get to find out. :)
If you don't like a pull request close it or ignore it. But disabling accidental and “drive-through” pull requests sounds very bad to me.
On popular projects this happens often enough to become annoyance for maintainers.
I don't see any case when opening a pull request from someone else's branch and without a description could be done intentionally.
It does add an extra step if you wish to PR someone else's code (you now have to fetch it from their remote, push it to yours, and then make the PR vs directly cross-repo PR between two repos you don't own).
It's not a heavy extra step though and I don't see this as removing the ability for any number of small PRs.
What does: "the changes are not explained in the commit body" actually mean?
Is this opt in?