Still loving Graphite! But I've been running into ...
# report-bugsk
Kael Shipman
10/24/2025, 8:03 PMStill loving Graphite! But I've been running into a really annoying bug lately: When you set something to "merge when ready" and it enters the merge queue, but then the CI fails and it ejects from the merge queue, fixing the issue does not automatically put it back in the merge queue. You actually have to uncheck "merge when ready" and then recheck it. This has happened to me multiples times today alone and it means I have to sit there and monitor my PRs, which is antithetical to the "merge when ready" option.
p
Pylon
10/24/2025, 8:03 PM(If applicable) To help us repro, please send the following if you haven't already:
- PR links, screenshots, and/or debug output if applicable
- Repro steps
- Does this happen consistently? Just to you or others on your team also?
- Is this a regression? Is the problem new?
- If you're having an issue with the CLI, please send us debug logs using
gt feedback --with-debug-context <any message>Pylon
10/24/2025, 8:12 PMhey Kael, thanks for your feedback here. To be clear on what's happening, you're using Graphite's merge queue and after you submit a change to the PR the CI checks rerun and pass but the PR is not re-enqueued into the merge queue despite the Merge When Ready being toggled on?
k
Kael Shipman
10/24/2025, 8:12 PMCorrect!
p
Pylon
10/24/2025, 8:14 PMgotcha, we're roadmapping improvements to the Merge When Ready functionality and I'll include this in our internal tracking issue for them 👍
k
Kael Shipman
10/24/2025, 8:14 PMLove it, thanks! 🙏
Kael Shipman
10/24/2025, 8:57 PMJust happened again. Not sure how access works for you guys internally, but here's the link to the PR.