Hello! We've just enabled the Graphite merge queue...
# report-bugs
a
Hello! We've just enabled the Graphite merge queue and have seen a couple of graphite merge queue PRs fail when there didn't seem to be anything wrong with them - I think it might be because the graphite protections check reported failure, even though all the CI either passed or was skipped. Possibly it ran too early and then never got re-triggered
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>
a
An example is this branch: gtmq_spec_47d0dc_1755257320376-2669f983-0e4f-44d2-af45-d53bf56e06bc
Is this bug or a misconfiguration on our end?
p
hey Anna, could you please share a link to a PR where the failure occurred?
Also happened here, this time with a timeout error https://github.com/LindusHealth/monorepo/pull/11790 Not every PR is affected but hitting a few times every day
Another one here that hit the same PR multiple times: https://github.com/LindusHealth/monorepo/pull/11835
This is proving quite disruptive for our team - please could we get some help on this? Thanks!
p
hey Anna, confirming we received your in-app feedback as well. Will be looking into this today 👍
❤️ 1
hey Anna, we've spelunked in the logs on our end and found that as you suspected it is the protections check not succeeding which is blocking the merges. We don't think you need to mark that as a required check- we use it internally and we don't set it to be required.
a
Thanks so much for looking into it! Will try that out
What exactly is the protections check used for internally - shouldn't that block the merge whatever if it fails, even if we've set it as a non-required check? Or is it used by Graphite in other scenarios
When you say "mark as a required check", are you talking about Github status checks, or is that a setting somewhere in Graphite?
We actually don't have any required status checks set in the Github branch protection rules for this branch
Screenshot 2025-08-20 at 15.31.06.png
In Graphite, we don't have a required status check for graphite protections either.
p
ah this is a separate Graphite-based feature called Protections that's enabled in your org. It's been configured here: https://app.graphite.dev/protection
a
Doesn't look like merge gatekeeper depends on Graphite protections either
p
I'm not sure of the specifics there but in the merge queue's logs we can definitely see it's the Graphite Protections check preventing the merges so that feature may need to be tweaked or disabled to see if that resolves it. (For context about Protections it's still a beta feature and it's not being actively worked on for the foreseeable)
a
Ah, understood. I think right now, Graphite protections is a lot more valuable for us than the merge queue, so sounds like we either need to live with the bug or disable the merge queue again