Bitbucket + KeySigner

Identify who controls repository access and branch restrictions in your workspace.

What to check first

Use a test repository to confirm which changes require a reviewer and ensure another workspace administrator can restore access.

KeySigner setups

KeySigner setup requirements →

Provider availability

Blocking merges when checks fail. Requires Bitbucket Cloud Premium. Check provider requirements →

Provider walkthroughs

What it covers

Protecting a maintainer account does not change permissions already given to build credentials.

Make an offline recovery plan →

Troubleshooting

Is a signed change rejected when you push it?

Check the signed-commit requirement on the exact repository and verify that Bitbucket can associate the signature on the rejected commit with a known key. If Bitbucket rejects the credential before you reach that check, note that app passwords stopped working for Git over HTTPS and API requests on July 28, 2026.

Replace retired credentials for Bitbucket, npm, and PyPI →

Check Bitbucket status for reports on Bitbucket Cloud.

Find documentation and support →

Documentation and support

Bitbucket documentation

Check requirements for signed commits

KeySigner setup help

Ask about this setup →