DESTRUCTIVE (forced) git branch deletion is MISCLASSIFIED and requires NO PERMISSION
- 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
Per `/diagnose`:
---
Found it. The root cause is clear from the event log:
- **`git push --delete`** at 20:42:24 → generated a `permission.request` event → you were prompted ✅
- **`git branch -D`** at 20:43:03 → **no `permission.request` event at all** → ran silently ❌
The CLI classifies commands by identifier to determine if they're read-only. In the `git push` permission request, `git push` is correctly tagged `"readOnly": false`. But earlier in the session, `git branch -r` was tagged `"readOnly": true` — and the classifier appears to treat **all `git branch` invocations as read-only**, regardless of flags like `-D`.
In short: **this is a classifier bug in the CLI**. It doesn't recognize that `git branch -D` is destructive, so it skips the permission prompt entirely. `git push --delete` was correctly flagged; `git branch -D` was not.
This is worth reporting via `/feedback` — the `git branch` command classifier needs to recognize `-D` / `-d` / `--delete` as write operations.
### Affected version
GitHub Copilot CLI 1.0.71.
### Steps to reproduce the behavior
- Ask Copilot to delete one or more remote branches to provoke it to call `git push --delete ...`.
- Observe that the command requires user acknowledgement.
- Ask Copilot to delete one or more local branches to provoke it to call `git branch -D ...`.
- Observe that the command runs with no permission prompt.
### Expected behavior
A destructive operation such as DELETING A BRANCH should require confirmation by default.
### Additional context
_No response_
Guía de contribución
Línea de trabajo
Comienza en el clasificador de comandos CLI e inspecciona cómo se asignan los identificadores de git branch a los eventos readOnly y permission.request. Reprodúcelo con git branch -D, -d y --delete, y verifica después que las variantes destructivas requieran confirmación, mientras que git branch -r siga siendo de solo lectura.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- git
- Área
- cli, security
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 55/100