7 ms·
Why do they have to sign their commits? Their contributions are unverified, as are any commits made in your name without your signature, but they don't have to
by jeroenhd 5y ago
Why do they have to sign their commits? Their contributions are unverified, as are any commits made in your name without your signature, but they don't have to do anything.
You gain the ability to prove that a certain commit came from your machine or someone with full access to it, they don't.
To be honest, everyone should be signing their commits in a professional environment. It takes minutes of work to set up and greatly increases the trust you can have in the code base.
If you're scared of affecting your workflow, just don't protect the GPG keys with a password (dangerous) or use your operating system's trust store to unlock them at login (less dangerous, but still suboptimal).
I sign my work commits without ever entering a password in a prompt. Some of my coworkers also sign their commits, most of them don't.
- bentcorner 5y agoIf you don't sign your commits you leave yourself an escape hatch just in case you need to wash your hands of a PR. /s
- teitoklien 5y agoThanks a lot for explaining it ! I’ll start using it then