[Graphite blocks merge on a passing required check when its parent check suite is cancelled] Hey team 👋 We've hit a consistent issue where Graphite shows a required check as pending and won't merge-when-ready, even though the check has passed and GitHub itself considers the PR mergeable. We have a custom aggregating required status check driven by `workflow_run`/`check_suite` events. We post its result to the PR's head SHA via the Checks API. GitHub then auto-assigns that check run to another workflow's check suite on the SHA (there's no API field to control suite membership). The problem we're seeing is that during restacks, if the auto-assigned suite is cancelled, Graphite appears to evaluate the parent check suite's conclusion and treats our check as unresolved, leading to it showing

pending

and blocking merge. But the check run itself is success, and GitHub reports the PR as MERGEABLE because branch protection matches required checks by name, not by suite. Could Graphite evaluate a required/named check by the latest check run of that name, rather than the conclusion of its parent check suite? Or if you think my conclusions are incorrect, I'd love any debugging help you can offer! Can DM you example PRs if helpful. Thank you! 🙏

Hey There! I will be more than happy to help with this. Can you please link me a Graphite PR link where it still shows the check pending while GitHub is mergable? This will allow me to debug it on the backend and see if I can't provide a solution. Thanks!

Thanks so much, will DM you 🙂

I will say my team is also experiencing this. I had not had time to dig into the issue but what Helen is saying sounds right.

Dylan can you give me a Graphite PR link where this is happening? Thanks!

I can! Does it need to be one thats open still or is merged okay? I can probably provide both

Open still would help!