hey all. we're having issues with github actions a...
# how-do-i
l
hey all. we're having issues with github actions and graphite. we have sql migration that runs on prs on main that are closed. but only the bottom diff in a stack is triggering this. wondering if we should try triggering on push to main instead and if there are any other settings we should try?
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
Hey Luke, could you share your action trigger? Is it possible its only targeting branches that target [main]? do you have an example of a PR/stack where this happened?
l
yes it only targets main because these migrations are on our prod database and we only want them to run when something lands to main
Copy code
name: CD - Auto Migration

on:
  pull_request:
    branches: [main]
    types: [closed]
    paths:
      - "packages/dbs/liquidity-db/drizzle/**"
what happens is the bottom diff in the stack will trigger this when merging but the rest do not
p
Okay Luke, i see why this is happening. The current setting configuration you have turned on will fast forward to the head of the stack at once (versus rebasing each PR to main first). You can actually see this in the PR page anything besides the bottom most PR does not target main. So at least 1 solution would be to keep the FF merge setting on but turn off the
CI settings
toggle so each PR rebases on main first triggering your job. Need to do a bit more research on if there is another way to trigger based on a new head and i think basing it on PR closed would have false triggers if you actually close a PR =/
l
we switched to run migrations on push to main and it works!