I ran into two usability problems in Copilot workspace sessions:
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 2.1k
- Fork
- 153
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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 |
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- git, github
- Ambito
- desktop, developer-experience
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 48/100