Hey Graphite team! We had a strange case in which Graphite states a PR failed in merge queue but Github still merged it, which ultimately resulted in a PR stuck with no changes. Is there someone that can help us debug what happened and why so we can explain it to our development team when it does happen (if it happens again)?

(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>

Here is the specific PR in question: https://app.graphite.com/github/pr/armadinsecurity/ares/12392 I am not sure that we've seen this previously so it does not happen often. This is more of a question of why did it happen and where is the disconnect between Graphite and Github.

Hey Mike, looking at my logs here i believe we actually succeeded at merging the first time around on 3/22/2026 and failed during a latter part of the process causing us to incorrectly fail the entire attempt. This is further indicated by the error on all subsequent attempts

Encountered an empty PR while trying to merge. This happens when a PR only contains changes that have already been merged.

This one is very odd, and ive not seen anything like it before / would not expect it to occur a second time. Will pass this along to the merge team to investigate how we can better handle situations like this where we succeed but not completely.