hi! is there any possible workaround to have PRs marked as "merged" instead of "closed" while using "Fast forward merge"? i know you all must get this question all the time, but we have users on graphite and github, and it's driving us up a wall.
p
Pylon
10/30/2025, 10:41 PM
(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
k
Kristina Shia
10/30/2025, 10:42 PM
We use the graphite merge queue and just enabled "Fast forward merge". Now if someone checks Github to look at a potentially problematic PR, it looks like the PR was closed not merged.
p
Pylon
10/31/2025, 12:24 PM
hey Kristina, that is expected behavior and a trade-off when the
CI Settings
is enabled in the merge queue's settings, which it is for this repo. More info in our documentation here.