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

Re: [RFC] Hook management via 'git hooks' command

From
Emily Shaffer <emilyshaffer@google.com>
Date
Nov 25, 2019, 22:45 UTC
Message-ID
<20191125224533.GB83137@google.com>
In-Reply-To
<20191125222113.GA83137@google.com>
> This sounds like we both are pretty close on the same page, so I think I
> will get started in the coming weeks and see if we can get a mockup to
> pick at with the implementation details in front of us.

Hm. To elaborate (and partially as a reminder to myself) I will try to get it done in the following order:

1. Implement 'git hook list <hookname>' which reads all the configs.
(User would need to manually add the configs at this stage)
2. (maybe) Implement 'git hook execute <hookname> <arg...>'. This may or
may not be useful; I suppose it would be pretty equivalent to:
 $ git hook list <hookname> | xargs -I% sh % <arg...>
3. Implement config modifiers like 'git hook add', 'git hook edit' etc.

My thinking is that we will have a lot of time with 1. in front of us to nitpick how we want the config format to look, how the ordering should go, etc. and it will be a fairly simple implementation. It'll also be "usable" although not in a particularly friendly way in case someone wants to try it and see, in a way that the config modifiers by themselves wouldn't be.

 - Emily
Previous: Emily ShafferNext: brian m. carlson
Message 8 of 12 in “[RFC] Hook management via 'git hooks' command”
  1. Emily ShafferNov 16, 2019
  2. brian m. carlsonNov 16, 2019
  3. Emily ShafferNov 18, 2019
  4. brian m. carlsonNov 19, 2019
  5. Emily ShafferNov 23, 2019
  6. brian m. carlsonNov 25, 2019
  7. Emily ShafferNov 25, 2019
  8. Emily ShafferNov 25, 2019
  9. brian m. carlsonNov 26, 2019
  10. Emily ShafferNov 26, 2019
  11. brian m. carlsonNov 26, 2019
  12. Emily ShafferDec 2, 2019

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.