Hello! Because not everyone is using Graphite around here, we’re testing out the GitHub merge queue instead of the Graphite one. There’s one behavior that felt surprising to me with a stack: I marked the stack as “merge when ready”, updated the stack, and waited. The first branch was added to the queue, then merged. All good. The second PR started to point to

main

and was added to the queue immediately. However, I was expecting Graphite to rebase it but it didn’t. So the commits from the first branch were there, along with the associated diffs, even though they didn’t make sense since

main

already had these changes (probably a GitHub problem). The issue for me is that it makes the PRs of a stack confusing and misleading. If someone goes back to that PR later, it won’t be clear what it actually changed. I know you recommend using your queue, but is there a solution to this? Is it the expected behavior when using the GitHub queue? I’d prefer taking the hit of another round of CI on that branch, if Graphite could automatically rebase instead of adding to the queue as-is.

(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

ok, good to know, thanks for confirming