I think auto merge is not triggered here since 2 checks fail with issue number and news entry. Maybe adding skip-news and skip-issue labels will help.

I think auto merge is not triggered here since 2 checks fail with issue number and news entry. Maybe adding skip-news and skip-issue labels will help.

I don't think so, this PR #10098 didn't have those labels and it was automerged.

The linked PR had both an issue number and a NEWS entry so it didn't require those labels and all checks passed. skip label is required when there is no issue in title and adding it makes the check pass and same for skip news. I hope it's the reason auto merge doesn't but I might be wrong.

The linked PR had both an issue number and a NEWS entry so it didn't require those labels and all checks passed. skip label is required when there is no issue in title and adding it makes the check pass and same for skip news. I hope it's the reason auto merge doesn't but I might be wrong.

I see, sorry 😅

The linked PR had both an issue number and a NEWS entry so it didn't require those labels and all checks passed. skip label is required when there is no issue in title and adding it makes the check pass and same for skip news. I hope it's the reason auto merge doesn't but I might be wrong.

You are right, reading the source tells miss-islington expects those checks to be successful too:

https://github.com/python/miss-islington/blob/2e69ff6506767bbfa6436585bfdad9d43f888ced/miss_islington/status_change.py#L98

No problem, TIL for me :)

Yes, the PR will only be automerge if:

• all status checks passed,
• and it's been approved by core dev,
• and CLA has been signed.

@andresdelfino: Status check is done, and it's a success ✅ .

Thanks @andresdelfino for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7.
🐍🍒⛏🤖 I'm not a witch! I'm not a witch!

@andresdelfino: Status check is done, and it's a success ✅ .

GH-10465 is a backport of this pull request to the 3.7 branch.