On Mon, May 13, 2019 at 05:51:01PM -0700, Jonathan Nieder wrote: > Hi, > > brian m. carlson wrote: > > > I've thought a lot about the discussion over whether this series should > > use the configuration as the source for multiple hooks. Ultimately, I've > > come to the decision that it's not a good idea. Even adopting the empty > > entry as a reset marker, the fact that inheritance in the configuration > > is in-order and can't be easily modified means that it's not likely to > > be very useful, but it is likely to be quite surprising for the average > > user. > > Can we discuss this some more? What would it take to make it likely > to be useful in your view? There are two aspects here which I think are worth discussing. Let's discuss the inheritance issue first. Order with multiple hooks matters. The best hook as an example for this is prepare-commit-msg. If I have a hook which I want to run on every repository, such as a hook that inserts some sort of ID (bug tracker, Gerrit, etc.), that hook, due to inheritance, *has* to be first, before any other prepare-commit-msg hooks. If I want a hook that runs before it, perhaps because a particular repository needs a different configuration, I have to wipe the list and insert both hooks. I'm now maintaining two separate locations for the command lines instead of just inserting a symlink to the global hook and dropping a new hook before it. I don't think there's a good way to make it easier unless we radically customize the way configuration is done. I don't doubt that there are a small number of configurations where the inheritance behavior is fine—I believe GitHub's backend is one of them—but overall I think it's hard to reason about and customize. The second issue here is that it's surprising. Users don't know how to reset a configuration option because we don't have a consistent way to do that. Users will not expect for there to be multiple ways to set hooks. Users will also not expect that their hooks in their configuration aren't run if there are hooks in .git/hooks. Tooling that has so far used .git/hooks will compete with users' global configuration options, which I guarantee you will be a surprise for users using older versions of tools. The new behavior, which puts everything in the same directory (.git/hooks) is much easier to reason about. I think we're obligated to consider the experience for the average end user, who may not be intimately familiar with how Git works but still needs to use it to get work done. It also provides a convenient place for hooks to live, which a config-based option doesn't. We'll need to invoke things using /bin/sh, so will they all have to live in PATH? What about one-offs that don't really belong in PATH? > > I think a solution that sticks with the existing model and builds > > off a design used by other systems people are familiar with, like cron > > and run-parts, is going to be a better choice. Moreover, this is the > > design that people have already built with outside tooling, which is a > > further argument in favor of it. > > To be clear, the main advantage I see for config versus the .git/hooks > model is that with the config model, a user doesn't have to search > throughout the filesystem for .git/hooks directories to update when a > hook is broken. I agree this is an advantage if they don't hit the ordering issue. I think a lot of the common use cases where this approach has benefits can be handled well with core.hooksPath and hooks that can turn themselves on or off depending on the repository config. What might be an interesting approach that would address these concerns is a core.globalHooks[0] option that points to a set (or sets, depending) of multiple-hook directories. We then enumerate hooks in sort order, considering both the global and the local directories as one unit, perhaps with some way of disabling hooks. I'm not planning on working on this myself, but I wouldn't be opposed to seeing someone else work on it. [0] Better name suggestions are, of course, welcome. -- brian m. carlson: Houston, Texas, US OpenPGP: https://keybase.io/bk2204
Attachment:
signature.asc
Description: PGP signature
