Re: Protecting master branch on GitHub?

--===============6146701337747713175==
Content-Type: multipart/alternative; boundary="94eb2c03e44254299f05578b17d5"

--94eb2c03e44254299f05578b17d5
Content-Type: text/plain; charset="UTF-8"

How do people feel about changing our policy to say changes
should all happen via pull requests (and take advantage of the
GitHub settings to enforce this)?


In my case: strongly in favor

--94eb2c03e44254299f05578b17d5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div class=3D"gmail_extra" dir=3D"auto"><div class=3D"gma=
il_quote"><br><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
How do people feel about changing our policy to say changes<br>
should all happen via pull requests (and take advantage of the<br>
GitHub settings to enforce this)?<br></blockquote></div></div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">In my case: strongly in favor</div><div cl=
ass=3D"gmail_extra" dir=3D"auto"><div class=3D"gmail_quote"><blockquote cla=
ss=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex"></blockquote></div></div></div>

--94eb2c03e44254299f05578b17d5--

--===============6146701337747713175==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Biopython-dev mailing list
[email protected]
http://mailman.open-bio.org/mailman/listinfo/biopython-dev
--===============6146701337747713175==--