Answer: To troubleshoot hooks, use the troubleshooting table: verify the JSON file is in the .github/hooks/ directory, check for valid JSON syntax, ensure version: 1 is specified, verify the script is executable, and check for a proper shebang. For timeouts, the default timeout is 30 seconds and you can increase timeoutSec in the configuration. Status: Confirmed Entry: tool/github-copilot/troubleshooting/troubleshoot-hooks Revision: 2 Digest: sha256:211120c286e8bf10 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:24:13Z Last changed: 2026-11-16T12:46:14Z (JSON validation command: — → jq . hooks.json) Last verified: 2026-11-20T13:02:33Z Next check: 2026-11-21T13:02:33Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of default timeout | 30 seconds | seconds | [1] | 2026-11-20 hooks directory | .github/hooks/ | | [1] | 2026-11-20 required version | version: 1 | | [1] | 2026-11-20 timeout setting | timeoutSec | | [1] | 2026-11-20 executable check | chmod +x script.sh | | [1] | 2026-11-20 shebang example | #!/bin/bash | | [1] | 2026-11-20 JSON validation command | jq . hooks.json | | [1] | 2026-11-20 Sources: [1] GitHub. "Using hooks with GitHub Copilot CLI - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/use-hooks Role: primary. Accessed: 2026-11-20T13:02:33Z Quote: "The default timeout is 30 seconds." (Supports: default timeout) Quote: "Verify the JSON file is in the .github/hooks/ directory." (Supports: hooks directory) Quote: "Ensure version: 1 is specified in your hooks.json file." (Supports: required version) Quote: "Increase timeoutSec in the configuration if needed." (Supports: timeout setting) Quote: "Verify the script you are calling from your hook is executable ( chmod +x script.sh )" (Supports: executable check) Quote: "Check that the script has a proper shebang (for example, #!/bin/bash )" (Supports: shebang example) Quote: "Check for valid JSON syntax (for example, jq . hooks.json )." (Supports: JSON validation command) Snapshot SHA-256: 8c9c2c55a04a453ab719b847329e13467b444678db40077c5c70c8086a8bfd8b (captured 2026-11-19T12:56:21Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:56:22Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:02:33Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:02:33Z Last attempt: 2026-11-20T13:02:33Z Notes and limitations: Extracted automatically from a single official source (section "Troubleshooting"). Related: https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-last-activity-at How do I troubleshoot inaccurate last_activity_at data for GitHub Copilot users in my organization? https://latestn.com/tool/github-copilot/troubleshooting/unsupported-host-sandboxing What happens if my host does not support local sandboxing in GitHub Copilot? https://latestn.com/tool/github-copilot/troubleshooting/verify-ai-sme-answers How do I verify GitHub Copilot CLI answers before trusting them when using it as an AI SME? https://latestn.com/tool/github-copilot/troubleshooting/test-mcp-server-independently How do I test an MCP server independently in GitHub Copilot? https://latestn.com/tool/github-copilot/troubleshooting/test-plugin How do I test a GitHub Copilot CLI plugin locally? https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-custom-instructions How do I troubleshoot GitHub Copilot code review when custom instructions are ignored or behave inconsistently? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-16T12:46:14Z | changed | JSON validation command: — → jq . hooks.json | [1] 2026-11-16T12:46:14Z | changed | shebang example: — → #!/bin/bash | [1] 2026-11-16T12:46:14Z | changed | executable check: — → chmod +x script.sh | [1] 2026-11-16T12:46:14Z | changed | executable permission command: chmod +x script.sh → — | [1] 2026-11-16T12:46:14Z | changed | Windows JSON validation command: ConvertTo-Json -Compress → — | [1] 2026-11-16T12:46:14Z | changed | Unix JSON validation command: jq -c → — | [1] 2026-11-13T03:24:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-hooks/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/troubleshooting/troubleshoot-hooks POST: https://latestn.com/dispute/tool/github-copilot/troubleshooting/troubleshoot-hooks with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/troubleshooting/troubleshoot-hooks?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I troubleshoot or debug hooks in GitHub Copilot CLI? Revision 2, last verified 2026-11-20T13:02:33Z. https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-hooks (accessed 2026-11-21T09:59:43Z). @misc{LatestN_tool_github_copilot_troubleshooting_troubleshoot_hooks_r2, title = {How do I troubleshoot or debug hooks in GitHub Copilot CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-hooks}}, note = {Revision 2; digest sha256:211120c286e8bf10; last verified 2026-11-20T13:02:33Z; accessed 2026-11-21T09:59:43Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/troubleshooting/troubleshoot-hooks