Presently, as originally added per#29 and most recently discussed and further documented perpython/devguide#518 , CPython PRs are auto-merged by the bots via theautomerge GItHub label. However, for a while now, GitHub has now implemented abuilt-in, native automerge feature, which is integrated with the GitHub UI, familiar to devs on other repos, can be customized in the repo's branch protection settings, and doesn't require a bunch of bespoke code and processes on our end.

Do we need to continue maintaining and using the bespoke label-based bot automerge, or can we switch to using the standard, built-in GitHub feature?

One thing I can think of is automerge being triggered automatically onmiss-islington PRs—but perhaps that could be changed to just having miss-islington enable GitHub automerge on the PR through the API, if that's possible?