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.

制限事項

 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 プランのお客様のみ

Requiring signed commits within a workspace, project, or repository 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.

署名済みコミットの必須化

チームのワークフローに与える影響

有効

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

無効

  • 過去のコミット: 過去のコミットに変更は適用されません。

  • コミットのプッシュ: リポジトリにプッシュされるコミットへの署名は必須ではありません。チェックや強制の仕組みはありません。つまり、署名されていないコミットもエラーなしでプッシュできます。

  • ブランチのマージ: ローカル ブランチのマージは、コミットの署名のチェックなしで実行できます。署名を検証せずに複数のコミットのマージが許可されます。

More information on using GPG or SSH keys to sign commits

 

 

さらにヘルプが必要ですか?

アトラシアン コミュニティをご利用ください。