Huh, the web-based editor doesn't seem to make the branch on your own repo, but in the same repo as the project. Oops! We should make sure that we delete this branch once done.

That's weird about the web-based editor making a branch in the main repo. I feel like it didn't used to do that, but I don't use that feature very often. I hope that only happens for those of us with commit rights to matplotlib (and I suspect it does) otherwise it's a definite authorization violation.

It's a new feature that it allows you to create a branch and make a PR. It just used to directly edit files in the current branch.

I am pretty sure I remember some people contributing tiny patches to us
from the editor before that didn't have commit rights. I suspect my issue
is that I have commit rights, so it picked this repo instead of my fork. I
probably should have done the edit in my fork instead, but I am not sure it
would have made a PR against matplotlib's repo. Weird.

On Wed, Dec 9, 2015 at 10:34 AM, Jens Hedegaard Nielsen <
notifications@github.com> wrote:

It's a new feature that it allows you to create a branch and make a PR. It
just used to directly edit files in the current branch.

—
Reply to this email directly or view it on GitHub
#5644 (comment)
.

@WeatherGod If you do it agains a repo where you don't have rights it does indeed fork however if you had rights it used to only allow you to edit the files in place on the branch.

This looks good to go.

backported to v1.5.0-doc as 37f08ba