We're very interested in using signed commits but are struggling to figure out how to use it in the real world. Would love some advice from those who know more. We think we know how to deal with signed commits & auto-reject such commits at build time, as well as clean up. But we're worried that folks won't sign on the way in accidentally. We don't know of a good way to force the team to always sign commits yet, especially as they get new machines and what hav eyou. Is there a way to add something to the repo config to force, or at least default, this? We considered forking git and forcing this on the team, forcing them to sign for our repos. But we'd love to avoid this sort of heavy-handed approach. Thx! Eric -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html