Skip to content

Hooks cannot be scoped at a project-specific level in a monorepo #3561

@Yajur-Grover

Description

@Yajur-Grover

Describe the bug

When trying to create custom hooks for my project in my project-specific .github/hooks.json, the hooks do not get recognized by the CLI (after restarting the session). I am working within a monorepo, and it seems like hooks only get picked up in the root .github/hooks.json, which I cannot do since I want my hooks to be project specific.

I am not sure why this is an issue, since I know skills can be picked up at the project specific level by the CLI.

Affected version

GitHub Copilot CLI 1.0.55

Steps to reproduce the behavior

  1. Create a hooks.json with some hooks in a project-specific .github/ (not in the root of the repo)
  2. Observe CLI not pick up the hook
  3. Create the hooks in the repo-root .github
  4. Observe the CLI pick up the hooks

Expected behavior

CLI should be able to pick up project-specific hooks.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:configurationConfig files, instruction files, settings, and environment variablesarea:pluginsPlugin system, marketplace, hooks, skills, extensions, and custom agents

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions