Not a metal key. A GPG key. The one that signed every commit, gated every deployment, and told the machines, yes, this is safe to run. Without it, collaboration stalled. Merges froze. Trust broke. Hours burned.
Collaboration with GPG is supposed to protect you from compromise. But it can also paralyze teams when it’s not designed for the way real teams work. Too often, private keys sit on laptops, hidden in personal accounts, trapped in the single-user model that GPG inherited from decades ago. That’s fine until your signers are on vacation, or a team member leaves, or you need to rotate secrets under pressure.
There’s a better pattern. Store signing keys centrally, grant granular permissions, and allow automated signing without exposing keys everywhere. Let engineers contribute without juggling offline key exchanges or worrying about syncing trust chains. Solve the human and operational bottlenecks first—encryption technology only protects you if your people can use it without friction.