Harry Dobrev

@thelinuxlich can you provide your config and how do you imagine this working in terms of configuration API?

It might work if we reverse the order in which `run-if-changed` processes the state. Currently, it asks Git for the changed files and tries to find matching patterns for each...

Hm, actually `run-if-changed` already does that in the order I described, but in the process of flattening the commands the order can get scrambled: https://github.com/hkdobrev/run-if-changed/blob/d0b41c3859391658b880b67b32b92bb52edb32f4/src/resolveMatchingPatterns.js#L3-L11 Might need to play with...

@thelinuxlich OK, I tried this something very close to your config. It does work like you would expect. It goes through the configured patterns in order. The alphabetic order doesn't...

I could implement this after Git introduces an environment variable for which hook ran a script. Depends on https://github.com/git/git/pull/1271 Husky also doesn't offer a way to see which hook ran....

Need to bump the NodeJS version to 20+ if we want the listr2 @ version 9