Steve Dower's workflow is to use git merge origin/master, and he did that earlier today, causing the most recent flurry. His repo is a fork of cpython but its master branch is 1000s of commits behind, so probably there's some bug in GitHub where the commits being merged are seen as new.

Mariatta, maybe this info helps the GitHub folks figure out how to fix this.

On Tue, Apr 6, 2021 at 10:02 AM Guido van Rossum <guido@python.org> wrote:

I don't have much to add (this occurs to me too and I just bulk-delete the messages) but I wonder if the problem might be caused by a situation where GitHub doesn't realize that a repo is a fork of cpython? I suppose that could happen if someone creates a fresh repo and pushes a local clone of cpython to it. I'll ask Zooba what he did.
--
--Guido van Rossum (python.org/~guido)
Pronouns: he/him (why is my pronoun here?)