Two named hook templates default to running inside the cloud session rather than on your machine.
gh-api-readonly and ruff-autofix are the default cloud-runnable ids within the disabled device-hooks path.
What's wrong with this entry?
Instead of calling back to your machine, a matching hook can be uploaded and run inside the cloud session. When the caller names no list, the ids permitted to do that default to gh-api-readonly and ruff-autofix; anything else falls back to running on your machine with a notice.
- A digest mismatch, a legacy copy, a matcher that does not match, or two consecutive "awaiting upload" results each demote a template back to local execution.
- Behind the same device-hooks gate that is off in this build.
is not run in the cloud in this version; it runs on this machine instead.
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.234
SessionEnd hooks lose the
bypass_permissions_disabledreasonBoth mention hook
-
v2.1.236
Hooks and Ctrl-C go quiet once shutdown has started
Both mention hook
-
v2.1.236
Shutdown seals transcript writes and gives SessionEnd hooks more time
Both mention hook