Changes pane is a gamechanger - I love it and all its functionalities.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
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 |
Contributor guide
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100