> On Nov 25, 2016, at 5:12 AM, Joshua Root <j...@macports.org> wrote: > > On 2016-11-25 16:08 , Lawrence Velázquez wrote: >>> On Nov 24, 2016, at 11:33 PM, Ryan Schmidt <ryandes...@macports.org> wrote: >>> >>> 6 copies of these changes arrived to the list: 1 when you created the >>> branch, 4 when you updated the branch (perhaps by force-pushing to >>> it?), and 1 when you merged the branch to master. >> >> Yeah sorry, I force-pushed a few times (and once more coming). Did not >> remember that force-pushes generate emails until after I opened the PR. >> >>> How can we avoid that? >> >> It's probably simplest to discourage opening PRs using branches on our >> organization's repositories. It seems that most PRs so far have used >> forks anyway, so committers should just continue doing so (and I should >> *start* doing so). > > Wait, how did you force push to a macports repo? I thought we disabled that.
It can only be disabled on a per-branch basis. We disabled it for master and the release branches, but when a developer creates a new branch, it's unprotected.
