sessionStart hook in .github/hooks/ does not fire in Copilot CLI (v0.0.420)
- Lenguaje dominante
- Shell
- Estrellas
- 11.2k
- Forks
- 1.9k
- Merge medio
- 14 h 16 min
- PR fusionados (30 d)
- 6
Descripción
### Describe the bug
`sessionStart` hooks defined in `.github/hooks/*.json` do not execute when starting a Copilot CLI session.
### Environment
- **CLI version:** v0.0.420
- **OS:** Windows 11
- **Shell:** PowerShell 7
### Hook configuration
**File:** `.github/hooks/test-hook.json`
```json
{
"version": 1,
"hooks": {
"sessionStart": [
{
"type": "command",
"bash": "echo \"Session started: $(date)\" >> logs/session.log",
"powershell": "Add-Content -Path logs/session.log -Value \"Session started: $(Get-Date)\"",
"cwd": ".",
"timeoutSec": 10
}
]
}
}
```
### Expected behavior
`logs/session.log` should be created with a timestamp entry when a CLI session starts.
### Actual behavior
`logs/session.log` is never created. The `sessionStart` hook does not fire.
### Additional context
```
Guía de contribución
Línea de trabajo
Reproduce the report using .github/hooks/test-hook.json with Copilot CLI v0.0.420 on Windows 11 and PowerShell 7, then check whether logs/session.log is created at session start. Trace the sessionStart hook entry point and verify the command is dispatched; done means the hook runs and writes a timestamped log entry.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- powershell, shell
- Área
- cli, tooling
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100