[BCLOUD-3166] Support signed commits for Git (BB-319)

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.
Latest Update:

Hide

This item is tracked on our public roadmap as we continue to iterate on this work

https://www.atlassian.com/wac/roadmap/cloud/enforced-signed-commits?search=signed&p=d704eead-54

Show
This item is tracked on our public roadmap as we continue to iterate on this work https://www.atlassian.com/wac/roadmap/cloud/enforced-signed-commits?search=signed&p=d704eead-54

Check for and display a 'verified' icon or something as well.

We just launched support for signed commits using SSH keys so users can now sign commits using both GPG and SSH keys.

This release did not include the ability to retroactively identify/link old commits. That is instead being tracked in the request BCLOUD-23508

is duplicated by

BCLOUD-21251 git .mailmap should be applied to user display names and emails

BCLOUD-13552 As a repo admin I want to see which user pushed each commit in my repo - Customer request

is related to

BSERV-9983 Show whether or not commits are signed in commit log

BCLOUD-22536 Add Verify Committer option

ENT-1016 Failed to load

relates to

BCLOUD-23508 Backfill git signed commit signature

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 relates to, 1 is depended by, 7 mentioned in)

Bitbucket Cloud