I looked into this and it looks like there's a blindspot in the Github API
reporting where it includes a bunch of checks that finished but doesn't list
checks that haven't started yet at all. In this case the bot reports success
because there are no pending checks.
Not sure how we can easily
> On 4 Sep 2021, at 22:15, Eric V. Smith wrote:
>
> Is it because I didn't wait for the checks to complete before merging?
>
> (It's a documentation only change that I previously committed to main without
> incident, so I didn't feel the need to wait for all of the checks to run
> before
Hi Eric,
The bot source code and bug tracker can be found at:
https://github.com/python/miss-islington
Victor
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
Thanks. I'll continue to ignore them, unless I hear otherwise on this list.
Eric
On 9/4/2021 5:42 PM, Guido van Rossum wrote:
I see this all the time and just ignore it. I have a feeling it's due
to the miss-islington bot being triggered by some event and checking
in on the PR while it is
I’ve had some pretty weird interactions with that bot too:
https://github.com/python/cpython/pull/27397
I’ve found in general that these messages are pretty noisy, and not very
helpful. For example, backporting a PR to another branch usually results in me
receiving around a dozen different
I see this all the time and just ignore it. I have a feeling it's due to
the miss-islington bot being triggered by some event and checking in on the
PR while it is still transitioning. Occasionally I see a very large string
of these and assume she's just having a bad day. Also notice that in your
