the graphite dashboard on a stack has

Waiting on CI...

with an alleged required check of

PR Gate

but this check does not show up on the actual github PR. This is blocking PRs from entering the merge queue

Hey Jason, is this still an issue? if so could you share the PR number / repo or graphite link so i can look though our logs?

yes this happens.. do you have access? app.graphite.com/github/…/… is an active one right now

Yes, you're onto the right mechanism. Graphite does apply the checks required for your stack trunk (

main

) when it decides stack mergeability / MQ entry. It is not inventing `PR Gate`; it is taking that required context from your ruleset/BPR and waiting until a check with that exact name reports on the PR. Mid-stack PRs whose base is not `main`/`gtmq_*` often won't show

PR Gate

on the GitHub Checks tab at all, which is why Graphite can look "more blocked" than GitHub. The always-green

PR Gate

pattern (require it on `main`/`gtmq_**`, auto-succeed for everything except graphite-bot) fights that model. Graphite will keep treating

PR Gate

as a real required check for landability, so if it never posts on normal stack PRs you get Waiting on CI and can't enter the queue. Recommended shape instead: 1. Put the checks you actually care about for mergeability as required on trunk, and make sure they run on stack/upstack PRs (or use Graphite CI Optimizations to skip mid-stack on purpose). 2. For heavier CI you only want in the merge queue, customize workflows on the

gtmq_*

branches Graphite creates for enqueued work: *https://graphite.com/docs/merge-queue-optimizations* 3. Drop the always-green

PR Gate

required check if its only job was to fake that split.