extended CI does not reliably trigger when auto-merge is on

Question

extended CI does not reliably trigger when auto-merge is on

BenWibking opened this issue 4 months ago · 3 comments

With the past few PR's I've merged (related to sanitizer warnings), the extended CI didn't trigger when I had auto-merge enabled. In all cases, I had to turn off auto-merge, then turn it back on. Then the extended CI triggered automatically.

Is it known why this is the case? It is just GitHub being flaky?

Answer 1 · 2024-06-19T16:46:03.000Z

Yeah, I have similar problems often (and often try the same trick as you did) but I don't know why this happens.

Answer 2 · 2024-06-25T00:44:12.000Z

IIRC the extended test are not triggered by changes made through the Github UI (like merging in develop or applying formatting).

Answer 3 · 2024-06-25T02:00:02.000Z

IIRC the extended test are not triggered by changes made through the Github UI (like merging in develop or applying formatting).

ah, that would explain some things...