I think this is a bug, though I'm not sure: When I click "Merge {N} PRs", it opens a dialog saying that I need to add commit signing. The problem is, I already have. When I click the link to github settings and try adding the graphite key again, I get a message that confirms that my key is already in github. I have noticed that sometimes graphite's app-driven restacking/rebasing does result in keys without my signature, and then I have to

git rebase -f --gpg-sign main

from my CLI to resign the commits. Not exactly sure what's wrong, but something definitely seems wrong with the signing key

Hey There! GitHub already has that Graphite key (the “subkeys already exist” error). When trunk requires signed commits, stack merge also checks that the PR author has Graphite commit signing set up, and app rebases were dropping signatures in some cases. We shipped a fix for the unsigned-rebase path this morning . Try a hard-refresh, then if any commits still look unsigned, resign with your CLI workaround,

gt submit

, and try Merge again. If you are still blocked then drop the PR link and I will take a fresh look!

Thanks for the fast reply! I haven't hit this issue yet today. I'll let you know when next I try to merge multiple PRs at once

Good Catch! Is it working as expected now?

Yep. Seems to be wroking Can I suggest that dialog's text should say "requires the PR owner to use commit signing"

Yep! Let me get this added to our improvements board. No ETA to relay but will get that over to the team for review. Thanks!