Answer: Create a new NAME.json file in the .github/hooks/ folder of your repository, paste the hook template, remove unused hooks, configure hook syntax under the bash and powershell keys (or reference script files), then commit the file to the repository and merge it into the default branch. Status: Confirmed Entry: tool/github-copilot/settings/create-repository-level-hook Revision: 2 Digest: sha256:9bd14d18ee160e6f (changes whenever the content changes) Timeline: Created: 2026-11-13T03:24:12Z Last changed: 2026-11-20T13:02:31Z (configuration keys: — → bash and powershell) Last verified: 2026-11-20T13:02:31Z Next check: 2026-11-21T13:02:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of file location | .github/hooks/ | [1] | 2026-11-20 file name pattern | NAME.json | [1] | 2026-11-20 template version | 1 | [1] | 2026-11-20 configuration keys | bash and powershell | [1] | 2026-11-20 final step | Commit the file to the repository and merge it into the default branch. | [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:31Z Quote: "in the .github/hooks/ folder of your repository" (Supports: file location) Quote: "Create a new NAME.json file (where NAME describes the purpose of the file)" (Supports: file name pattern) Quote: ""version": 1" (Supports: template version) Quote: "Configure your hook syntax under the bash and powershell keys, or directly reference script files you have created." (Supports: configuration keys) Quote: "Commit the file to the repository and merge it into the default branch." (Supports: final step) 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:19Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:02:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:02:31Z Last attempt: 2026-11-20T13:02:31Z Notes and limitations: Extracted automatically from a single official source (section "Creating a repository-level hook"). Related: https://latestn.com/tool/github-copilot/settings/create-user-level-hook How do I create a user-level hook for GitHub Copilot CLI? https://latestn.com/tool/github-copilot/settings/custom-certificates How do I add custom certificates for GitHub Copilot? https://latestn.com/tool/github-copilot/settings/custom-instructions-code-review How do I set up custom instructions for GitHub Copilot to perform thorough code reviews? https://latestn.com/tool/github-copilot/settings/configure-settings How do I configure settings in GitHub Copilot CLI? https://latestn.com/tool/github-copilot/settings/configure-user-clients-otel How do I configure users' clients for GitHub Copilot OpenTelemetry? https://latestn.com/tool/github-copilot/settings/copilot-app-repository-configuration How do I configure repository settings for the GitHub Copilot app? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:02:31Z | changed | configuration keys: — → bash and powershell | [1] 2026-11-20T13:02:31Z | changed | file name pattern: — → NAME.json | [1] 2026-11-20T13:02:31Z | changed | hook keys: bash and powershell → — | [1] 2026-11-13T03:24:12Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/settings/create-repository-level-hook/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/settings/create-repository-level-hook POST: https://latestn.com/dispute/tool/github-copilot/settings/create-repository-level-hook with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/settings/create-repository-level-hook?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I create a repository-level hook for GitHub Copilot CLI? Revision 2, last verified 2026-11-20T13:02:31Z. https://latestn.com/tool/github-copilot/settings/create-repository-level-hook (accessed 2026-11-21T09:52:55Z). @misc{LatestN_tool_github_copilot_settings_create_repository_level_hook_r2, title = {How do I create a repository-level hook for GitHub Copilot CLI?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/settings/create-repository-level-hook}}, note = {Revision 2; digest sha256:9bd14d18ee160e6f; last verified 2026-11-20T13:02:31Z; accessed 2026-11-21T09:52:55Z} } 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/settings/create-repository-level-hook