DevOps Interview DropAdvanced TierScenario+50 XP on read

Your organization wants signed commits for production code. How would you implement it?

Core Summary

git config user.email is free text, not identity, so signing is what turns authorship into a cryptographic claim. Roll out SSH signing, enforce it with branch protection and a trusted-key list, and plan for the parts that actually break rollouts: bots, squash merges, and key rotation.

Hints

Hint 1: git config user.email is free text, not identity

Hint 2: SSH signing is much easier to roll out than GPG

Hint 3: The hard part is bots and key rotation, not the signing

Reported in interviews at Google, Cloudflare, Chainguard