On 26 July 2017 at 02:21, Brett Cannon wrote:
>
>
> On Tue, 25 Jul 2017 at 07:30 Ben Hoyt wrote:
>>
>> With the linking back and forth, I'm curious why there wasn't a switch to
>> use GitHub's issue tracker when we switched to GitHub. I'm sure there was
>> previous discussion about this and good
On Tue, 25 Jul 2017 at 07:30 Ben Hoyt wrote:
> With the linking back and forth, I'm curious why there wasn't a switch to
> use GitHub's issue tracker when we switched to GitHub. I'm sure there was
> previous discussion about this and good reasons not to, but couldn't find
> those quickly (PEP 512
With the linking back and forth, I'm curious why there wasn't a switch to
use GitHub's issue tracker when we switched to GitHub. I'm sure there was
previous discussion about this and good reasons not to, but couldn't find
those quickly (PEP 512, Google search, etc) -- can someone point me in the
ri
On Sat, Jul 22, 2017 at 12:28 AM, Brett Cannon wrote:
> P.S.: Berker Peksag is working on providing commit emails with diffs in them
> which is the other most requested feature since the transition.
I forgot to give a status update on this. I deployed it on Heroku last
week. You can see an exampl
Thanks for working on this, Kushal and Brett.
Works great!
Mariatta Wijaya
On Fri, Jul 21, 2017 at 2:28 PM, Brett Cannon wrote:
> Thanks to Kushal Das we now have one of the most requested features since
> the transition: a link in PRs back to bugs.python.org (in a more
> discoverable way sinc
Thanks to Kushal Das we now have one of the most requested features since
the transition: a link in PRs back to bugs.python.org (in a more
discoverable way since we have had them since Bedevere launched :) . When a
pull request comes in with an issue number in the title (or one gets
added), a link
