• 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.

      Bitbucket Cloud currently lacks feature parity with Bitbucket On-Prem (Server/Data-Center), specifically for the ability to enforce a pre-receive hook that verifies that the user performing a push is exclusively pushing commits written by themselves, and not another user.
      This can also be useful to enforce that any commits written are written under expected committer details (username/email) that match the authenticating user account and not an unaffiliated account.

      Ref: "Verify Committer - rejects commits not committed by the user pushing to a repository."
      https://confluence.atlassian.com/bitbucketserver/using-repository-hooks-776639836.html#Usingrepositoryhooks-Defaultpre-receivehooks

            [BCLOUD-22536] Add Verify Committer option

            Roman Wolf added a comment -

            For SSH Key signing the recent blog article tells:

            "Repository admins can configure enforced signed commits using SSH keys as well!"

             

            Sounds similar to what is request in this ticket.

            Roman Wolf added a comment - For SSH Key signing the recent blog article tells: "Repository admins can configure enforced signed commits using SSH keys as well!"   Sounds similar to what is request in this ticket.

            Similar to, but not the same as https://jira.atlassian.com/browse/BCLOUD-3166

            Michael Walker added a comment - Similar to, but not the same as https://jira.atlassian.com/browse/BCLOUD-3166

              Unassigned Unassigned
              miwalker Michael Walker
              Votes:
              10 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: