Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Git branch or Worktree should be visible at all times in the chat window.

Abierto
  • ¿Algo no está bien?
#4,846 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
34/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, github
Área
desktop, developer-experience

Línea de trabajo

Start by reading the Changes tab and the app’s source control UI entry points; the issue does not name files or tests. Identify where the current branch or worktree is surfaced, then assess the requested branch switching, commit timeline, push, and branch creation controls. Done means branch or worktree stays visible and these actions are available in the UI.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Idk why I have to go to the terminal and do a git branch just to determine what branch I am on. The branch or worktree should always be shown, not just at the beginning of the chat. I should be able to change branches or worktrees easily in the UI without asking the bot to do it. I am trying to save tokens and it would be nice to be able to still do these things manually.

The Changes tab is okay but it is way behind the source control tab in vscode. I should be able to switch branches, see commit timelines, push commits and create branches in the UI without asking the bot to do it. This seems to be a major issue in all the agent IDEs I have used (cursor, codex, github, etc). I know you want to balance ease but remember there are technical people still in here and it would be nice to be able to turn on a technical mode or have this available in the side ribbon apps for people that still know what they are doing.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
2.2k
Forks
183
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/app

Todos los issues de github/app

Issues similares

Más issues de Desktop Dev

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.