github / github/app

Changes pane is a gamechanger - I love it and all its functionalities.

Offen
#2,764 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Keine Sprachdaten
Sterne
2.1k
Forks
153
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

Changes pane is a gamechanger - I love it and all its functionalities. Just an fyi - it is often not working! If we go by a step-by-step process, where we do some changes first, commit, then continue for other changes - it fails to referesh! The files tree reflects correctly the latest changes, but they are not "clickable" and do not appear in the code (changes window), which reflects only the previous changes. Asking copilot to refresh it does not help!

---
| Field | Value |
| --- | --- |
| App version | 1.1.6 |
| OS | Windows 10.0.26200 |
| Theme | Fox |
| Path | /chat |
| Tenure | Week 4 |

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Start by reproducing the issue in the Changes pane on the /chat path using the reported step-by-step flow: make changes, commit, then make more changes. Check whether the files tree is updated, clickable, and reflected in the code view after the commit. Done means the pane shows the latest changes without requiring a Copilot refresh request.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
github
Bereich
desktop
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
55/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.