On Tue, 4 Jun 2019 at 1:00 AM, Brett Cannon wrote:
> In the lock.yml you can specify to not leave a comment upon locking. See
> https://github.com/microsoft/vscode-python/blob/master/.github/lock.yml
> as an example.
>
We did this yesterday.
Sorry for the email spam folks! I completely misjudg
In the lock.yml you can specify to not leave a comment upon locking. See
https://github.com/microsoft/vscode-python/blob/master/.github/lock.yml as
an example.
On Sun, Jun 2, 2019 at 5:20 AM Ian Stapleton Cordasco <
graffatcolmin...@gmail.com> wrote:
> So the API endpoint to lock an issue absolut
Another issue with the lockbot: I was watching specific issues and PRs
because they're important to me (as a packager and a maintainer of
numpy.distutils. The locking has made it very hard to now follow any
updates. Even if someone opens a new issue or PR to continue where a locked
one, there's no
So the API endpoint to lock an issue absolutely does not require
comments on each thing. I think the idea is probably that it's easier
to understand that this was an automated process doing this rather
than being used in the vein of GitHub's moderation (which doesn't
account for anything other than
One thought - is it possible in github to subscribe to "everything
that isn't closed"? I couldn't see such an issue but that would (a)
let me ignore the lockbot messages, and (b) let me ignore close
threads so I wouldn't even need lockbot.
Paul
On Sun, 2 Jun 2019 at 12:26, Paul Moore wrote:
>
>
The bot has just been enabled, and it's catching up on historical bugs
(which can't be done all in one go, as rate limits would hit us).
Hopefully it should die down in a few days.
Whether there's a way to tell github not to send such notifications,
or whether it's possible for us to configure the
