Hi! We're trying to set up CI optimizations with g...
# how-do-i
s
Hi! We're trying to set up CI optimizations with github actions. I have it configured to be topmost and 1 bottom most PRs of a stack to run CI. I am noticing that if i have a stack: 1 <- 2 <- 3 <- 4 with 1,2,3 being "ready for review", and 4 being a draft, CI doesn't run on 3. Ideally, I would expect the topmost non-draft PR of a stack to run. Is this expected or configurable?
p
(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
s
Screenshot 2025-10-14 at 2.38.14 PM.png
i see a log in the action for the reason as
This PR is in the middle of a stack and is skipping CI due to your Graphite CI Optimizer settings.
oh looks like it's trying to run the topmost draft PR. Is there any way to have it run the topmost non-draft PR?
p
Hey Sidhu, yes unfortunately not being able to use only published PRs is a limitation of the CI optimization feature today.
s
sad parrot
p
One thing Ive seen folks do is fork the repo that gets called from the github action and customize it to their needs.
s
I was considering it. Is the API documented anywhere?
p
it is not
s
bummer, I assume it's not expected to be stable then?
p
yea i dont think we can make any guarantees here unfortunately
s
i guess i'll use a label to manually decide but a bit awkward. oh wells, thanks!
👍 1