Hi, question about required checks on stacked PRs with "merge when ready" (no merge queue). Our CI only triggers on PRs targeting trunk (

on: pull_request: branches: [develop, main]

), so intermediate PRs in a stack (which target feature branches) never run it. Our

develop

ruleset requires 3 checks, scoped to the default branch only — so GitHub doesn't require them on the intermediate PRs, but Graphite shows all 3 as "required to merge into develop / waiting on CI" on every PR in the stack, and they never post. The stack shows perpetually not-ready. 1. Is Graphite propagating trunk's required checks to every PR in the stack by design? 2. Any setting to stop it waiting on checks that don't run on intermediate PRs? 3. Does "merge when ready" still drain the stack bottom-up (CI fires once each PR's base becomes`develop`) — i.e. is "waiting on CI" just display, or does it actually block auto-merge?

Hey There! Yes and this by design, Graphite shows develop's required checks on every PR in a stack (merge readiness into trunk), even when GitHub doesn't on intermediate PRs. There's no toggle to hide those at this time. CI Optimizations (*https://graphite.com/docs/stacking-and-ci*) is the supported path so upstack PRs are treated as "runs later" once you wire the optimizer into your workflows. Merge when ready without a queue still works bottom-up, but each PR waits for real green checks. Thanks!