I'm a paid Graphite user using the Merge Queue. The graphite mergability check is taking over a minute to be added to newly created PRs. I have a mixed team with some using Graphite and some not. For graphite users I run different CI in PRs compared to non Graphite users and I use the mergability check to detect this. Previously it was only a few seconds, which meant I only had to wait 5 seconds to determine whether the PR was a graphite PR or not. But at 60+ seconds it means every non-Graphite user has to wait that time before CI starts running. Is this a known server issue on Graphite's side?

(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>

Something recently def changed in merge queue we are no longer able to use it, started yesterday

hey Marc, this is not a known issue from our end. The mergeability check uses GH's status check system so there could be latency there. Attila, this is unrelated to your issue with the merge queue.

Thanks. GitHub does seem to be having more frequent network issues lately. It seems like it's back to normal now..