{"version":"2.1.242","anchor":"two-hook-templates-are-allowed-to-run-in-the-cloud-by-defaul","canonical_anchor":"two-hook-templates-are-allowed-to-run-in-the-cloud-by-defaul","heading":"Two hook templates are allowed to run in the cloud by default","tier":"soon","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/two-hook-templates-are-allowed-to-run-in-the-cloud-by-defaul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Two hook templates are allowed to run in the cloud by default\n\nTwo named hook templates default to running inside the cloud session rather than on your machine.\n\n**What**\n\nInstead 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.\n\n**Details**\n\n- 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.\n- Behind the same device-hooks gate that is off in this build.\n\n**Evidence**\n\n`is not run in the cloud in this version; it runs on this machine instead.`\n\n- Area: Hooks\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}