Auto-merge triggers even though status-check did not pass yet.

[DavyLandman]

Select Topic Area

Question

Body

I think I've configured the required status-checks incorrectly, as I've seen the auto-merge triggering even if:

1. the required status item was skipped due to previous step failing
2. The moment the failing required item was restart it would get merged

This is the config:

For nr 1 this pr as an example:

usethesource/rascal-language-servers#437

Even though build didn't even run, bam it got auto merged as soon as it was skipped.

And for nr 2 I cannot find an example, as the retrigger of the failing build (which is sometimes a bit flaky due to perf issues on the mac runner) tends to complete it succesfully the second time around.

But I'm getting the feeling that I don't fully understand what "status checks to pass" mean exactly. Does anybody have some guidance?

(it might be related to #137211)

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[DavyLandman]

I've still been very carefull with this feature, not enabling auto merge unless I was sure I didn't need to restart a CI step.