Signed system commits and requiring signed commits

When you enable signed system commits, Bitbucket will use a system public GPG key to automatically sign the commits that it creates. This includes pull request merge commits, commits made by editing files in the browser, and accepted code suggestions in comments.

Using Bitbucket-signed commits will prevent failures and errors when you’re checking commits for signatures, having all signed commits merged into subsequent pull requests, or verifying commit signatures through your local Git installation. So you can be sure that you comply even with the strictest security and compliance standards.

Enable signed system commits

System commit signing is disabled by default. You need to be a workspace administrator to configure signed system commits.

  1. Select the Settings cog on the top navigation bar, and then select Workspace settings.

  2. Select the Automatically sign commits made through Bitbucket checkbox under Signed commits to enable system signed commits within the workspace.

  3. Select the Update workspace button to save your changes.

Limitations

 If the Automatically sign commits made through Bitbucket option is enabled in Workspace settings, and an admin has turned on the Require verified signature on all commits pushed from outside Bitbucket, merge strategies  Rebase Fast-Forward and Rebase merge are not supported.

Require signed commits (Premium plans only)

Premium plan customers only

Requiring signed commits within a workspace is only available to administrators in organizations with a Bitbucket Cloud Premium plan.

If you are on a Premium Bitbucket Cloud plan and are a workspace administrator, you can require that all commits are signed via Bitbucket.

  1. Select the Settings cog on the top navigation bar, and then select Workspace settings.

  2. Select the Require verified signature on all commits pushed from outside Bitbucket checkbox under Signed commits to require system signed commits within the workspace.

  3. Select the Update workspace button to save your changes.

Signed commits required

How it affects your team’s workflow

Enabled

  • Historical Commits: No changes are applied to historical commits. They remain unaffected after enforcement is turned on

  • Pushing Commits: Every commit that gets pushed to the repository must be signed. If a commit is unsigned or the signature is invalid, the git push command will fail with an error, preventing the push. This is the primary point where enforcement occurs

  • Merging Branches: Local branch merges can still be done without checks, and even if the commits being merged are unsigned, they can still be pushed. No signature validation will occur during or after the merge operation itself. The only check is during the actual git push, where commits in general must be signed

  • Pull Requests (UI-based): Pull requests created through the UI will not be subject to commit signing enforcement for milestone 1+2, however we will have concept of system signs for M3 where commit, PR made through UI will be signed by BB.

Disabled

  • Historical Commits: No changes are applied to any historical commits

  • Pushing Commits: Commits pushed to the repository do not require a signature. There are no checks or enforcement mechanisms in place, meaning unsigned commits can be pushed without errors

  • Merging Branches: Local branch merges can be performed without any checks on commit signatures. Multiple commits being merged are allowed with no signature validation

  • Pull Requests (UI-based): Pull requests created through the UI will not be subject to commit signing enforcement for milestone 1+2.

More information on using GPG or SSH keys to sign commits

 

 

Still need help?

The Atlassian Community is here for you.