You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merging an earlier PR in the stack via UI produces unsigned commits in the later PR(s) as a result of a rebase.
This might be due to a web config issue, but if so I've been unable to find it.
Before merging, commits in question, signed:
Before merging, state of play of earlier PR:
Before merging, state of play of later PR:
Post-merge, commits are rewritten and unsigned:
Our repos require commits to be signed, and this is interfering with CICD.
A local run of gh stack sync has been seen to resolve this, but it is a fair amount of overhead to perform each time we want a partial merge for review purposes.
bugBug Reportstopic: commit signingPartial merges and rebases produce unsigned or unverified commits.
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Merging an earlier PR in the stack via UI produces unsigned commits in the later PR(s) as a result of a rebase.
This might be due to a web config issue, but if so I've been unable to find it.
Before merging, commits in question, signed:
Before merging, state of play of earlier PR:
Before merging, state of play of later PR:
Post-merge, commits are rewritten and unsigned:
Our repos require commits to be signed, and this is interfering with CICD.
A local run of
gh stack synchas been seen to resolve this, but it is a fair amount of overhead to perform each time we want a partial merge for review purposes.All reactions