Corinne
12/17/2025, 11:56 PMgit log --show-signature on the code before it goes through the graphite merge que, it displays the correct email associated with my key ✅
• When my commit goes through the graphite merge queue, it gets signed with the incorrect email ❌
• For every repo I push code in that we don't have a graphite merge queue implemented, the correct email signs and verifies the commits ✅
Debugging Steps
• I have ran git config --global user.email "{my_email}"
• I have deleted the gpg key and created a new gpg key, ensuring it is associated with the correct email
• I have updated the email that should be displaying as signing commits to be used in communication preferences on Graphite and on GitHub and have made it my preferred email
• I have removed all keys associated with the incorrect email
My next step is to completely remove the incorrect email from my GitHub but I would lose all commits verified with that email. This feels like a security concern to my current company since commits are being signed with an email from an old company.
Would this be a "bug" or a "how-do-i"?Pylon
12/17/2025, 11:56 PMgt feedback --with-debug-context <any message>Pylon
12/18/2025, 2:43 PMSend feedback option from in the Graphite app's Help menu (shortcut is G then F) .
As this involves looking into your particular repos using merge queue and your email addresses I think we should continue this via an email thread, which sending the above feedback will create for us. Thanks!