Graphite Community

How should I setup my GitHub actions CI requirements if I use CI optimization? I found that if I just skip required tests that are optimized away, then Graphite can merge multiple PRs at once, even those that didn't get all checks run. I'm now adding a final check which fails if CI optimization was triggered. Is this the correct approach?

(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about:
- Screenshots / debug logs / list of commands you've tried to run so far
- Your workflow
- Current state


Hey Pim, The way that the CI Optimization works is, it will run CI on the bottom most PR, skip all middle Prs in the stack, and if enabled (true in your case), will also run on the top PR in the stack.
Once the bottom most PR merges, we perform automatic rebasing to point the second PR in stack to trunk. <https://graphite.dev/docs/merge-pull-requests#automatic-rebasing|See docs here> on automatic rebasing. This then triggers a run of CI on it.
So there is not a case that something merges that hasnt run through CI.

&gt; I'm now adding a final check which fails if CI optimization was triggered. Is this the correct approach?
&gt; 
Not sure i understand this one. Why would you need this?
