It looks like worktrees are implicitly created for sessions.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 2.1k
- Forks
- 153
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
It looks like worktrees are implicitly created for sessions. I think that there should be some prompt, at least the first time, to ask what branch the worktree should be created from.
For example, I was working my local dotnet/roslyn repo, which has both `origin` and `upstream` remotes. My `origin/master` branch is from ~2021. I think `upstream` has no `master` branch--we migrated from `master`->`main` naming. So I was super confused when the agent could not find stuff that I expected to be there.
If it had just asked me first (possibly recommending a default), what branch/ref to create the worktree off of, then the confusion could have been avoided.
---
| Field | Value |
| --- | --- |
| App version | 1.1.3 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 1 |
Guía de contribución
Línea de trabajo
Empieza rastreando el flujo de la sesión que crea worktrees implícitamente y, después, reprodúcelo con un repositorio que tenga varios remotes y ramas predeterminadas diferentes. Comprueba cómo se determina actualmente la selección de branch/ref. Se considera terminado cuando la primera sesión relevante solicita el branch base o ref para el worktree, tiene un valor predeterminado claro y evita elegir silenciosamente un branch inesperado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- git
- Área
- desktop, developer-experience, tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100