github / github/app

I ran into two usability problems in Copilot workspace sessions:

Abierto
#3,177 1 comentario 0 reacciones 0 asignados Ver en GitHub
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

I ran into two usability problems in Copilot workspace sessions:

1. Ignored files cannot be edited from the Files window
Files like app/etc/env.php are intentionally git-ignored because they configure the local environment. In Magento projects these files are essential for local development. The Files window/editor can hide or make ignored files read-only, which makes local environment setup harder than necessary. There should be a way to show and edit ignored local files, preferably with a clear warning that they are ignored/sensitive and should not be committed.

2. Changes window compares against master instead of the checked-out branch upstream
In a session checked out on a feature branch, the Changes window compares the branch against origin/master. That is not always useful. When working on an existing feature branch, I usually want to see only what changed locally after the last commit, or the difference between my local branch and origin/. Comparing everything to master shows the whole feature branch history and makes it hard to see my actual current changes.

---
| Field | Value |
| --- | --- |
| App version | 1.1.12 |
| OS | macOS 26.2.0 |
| Theme | Monochrome |
| Path | /chat |
| Tenure | Week 2 |

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Reproduce both reports in the Files and Changes windows using an ignored local file such as app/etc/env.php and a checked-out feature branch. Read the workspace session handling for file visibility/editability and branch comparison behavior; done means ignored files can be edited with a clear warning and Changes shows the selected branch's relevant local or upstream diff.

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

Evaluación

Stack tecnológico
git, github
Área
desktop, developer-experience
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
48/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.