The disableAllHooks notice now says SDK callback hooks still run while configured hooks are skipped.
What's wrong with this entry?
When the managed disableAllHooks setting is on, the skip notice now states that configured hooks are skipped while hooks supplied as SDK callbacks still run, instead of implying all hooks are off. The worktree-creation failure message no longer lists disableAllHooks as a possible cause.
- The worktree message now attributes a non-running hook to an untrusted workspace or a matcher that did not match.
- Hook invocation also passes storage and credentials through to the hook.
"WorktreeCreate hook failed: hook is configured but did not run (workspace not trusted or matcher mismatch)"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.229
Repositories can declare that all hooks are off
Both mention disable hook
-
v2.1.239
Plugin and hook forwarding now decided at startup, cloud workers only
Both mention disable hook
-
v2.1.239
Device hook forwarding worker added, off behind two flags and a kill switch
Both mention disable hook