git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Teams of people using signed commits...

From
EFEric Fleischman <efleischman@gmail.com>
Date
Jun 14, 2013, 19:02 UTC
Message-ID
<CABQymNKuwiOz-MQuM12fWSgBvBsBrykNYBqPBxCuSuxAC5cZZw@mail.gmail.com>

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

Next: Magnus Bäck
Message 1 of 3 in “Teams of people using signed commits...”
  1. Eric FleischmanJun 14, 2013
  2. Magnus BäckJun 14, 2013
  3. Fredrik GustafssonJun 14, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.