so i converted my renovate PRs into a stack to avoid having like 10 PRs occupying the merge queue for like 3 hours, and to avoid conflicts with the pnpm lockfile since it's extremely prone to conflicts. i have a stack of PRs and the one for updating

@vercel/functions

has passing CI, but for some reason i can't merge it as a stack? i was under the impression that merging as a stack wasn't dependent on the CI from the PRs under it in the stack? this is the branch for the 11th PR in the stack i want to merge:

renovate/npm-vercel-functions-3.4.1-to-3.4.2

(i don't want to merge

@google/genai

yet since it has something else) i was doing

gt move --onto <branch>

and for some reason, a bunch of them didn't trigger CI? not sure what i did wrong? i didn't do like

gh pr edit <pr> -- base <branch>

like i have occasionally before

(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

ah i did notice that one of the earlier ones in the stack for some reason targets graphite-base?

hey Ally, the presence of the

graphite-base/

branch there is indicative of some problem during the retargeting process. And GH API rate limiting during

submit

is known to interrupt retargeting. You are able to manually set the correct parent branch for the PR from in GitHub.

thank you!