The top PR of a stack that was fully in the merge ...
# report-bugsk
Kael Shipman
12/02/2025, 7:19 PMThe top PR of a stack that was fully in the merge queue erroneously ended up with 0 commits and was automatically closed without notification. I have no idea what happened but of course am not happy about it. I'm trying to recover the changes I had intended to commit now (which, thankfully were small). https://app.graphite.com/github/pr/rec-eng/monorepo/3883/%5BREC-7113%5D-Clean-up-temporary-code
p
Pylon
12/02/2025, 7:19 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
12/02/2025, 11:05 PMHey Kael,
Apologies for the inconvenience with this here.
I'm investigating this on our side, did you merge the entire stack at once?
Is this the first time you're seeing something like this?
k
Kael Shipman
12/04/2025, 3:44 AMyes, first time I've seen this, and yes, I put the whole thing in the merge queue