Ruud Kamphuis

Why not allow this configuration format too: ```json { "pre-commit": { "enabled": true, "actions": { "phpstan": { "action": "vendor/bin/phpstan" }, "phpunit": { "action": "vendor/bin/phpunit" } } } } ```

But adding `id` would also be good enough for me: ```json { "pre-commit": { "enabled": true, "actions": [ { "id": "phpstan", "action": "vendor/bin/phpstan" }, { "id": "phpunit", "action": "vendor/bin/phpunit" }...

When you specify an `id`, it should be unique (within the hook block).

My suggestion is to support 2 ways to declare it. If you use an object with keys in JSON, then you can use those as identifier. For all existing configurations,...

The other option where we add an id to the action declaration can also work. Only those that have an id can be triggered per action.

Good idea, I was also thinking of separating it. Thanks for thinking about it.

@greg0ire @derrabus Tagging you both, since you were also involved in https://github.com/doctrine/dbal/pull/6705. I'm happy to do the work, if you can guide me on the how and what!

Maybe it was caused by the fact that the branch did not yet have a parent yet (maybe the branch was created without git town).

``` git branch main + ruudk/2025/10/displayable + ruudk/2025/10/graphql-rename-trick * ruudk/2025/10/remove-from-response ``` As you can see, I have 3 work trees. ``` git town hack "ruudk/2025/10/fix-graphql-guard" --beam [ruudk/2025/10/remove-from-response] git checkout -b...

@kevgo I saw https://github.com/git-town/git-town/issues/5714 and https://github.com/git-town/git-town/issues/5720 so I think you are aware of more issues with worktree's. Today I had another weird situation. worktree 1 has main checked out, which...