/undo undid too much in a file
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
### Describe the bug
I was in the process of working on something with copilot CLI, had some uncommitted changes and then asked for another change. That last change didn't actually make sense, so I used `/undo` while the change was still executing (I think it was compiling). The state of the conversation reverted correctly, but the state of the file didn't: it reverted to no uncommitted changes.
I was able to restore the changes by telling copilot about it.
### Affected version
1.0.27
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by reproducing the issue with Copilot CLI 1.0.27: keep uncommitted changes, begin another change, and invoke `/undo` while it is compiling. Inspect the `/undo` flow and verify that completion preserves earlier uncommitted changes while reverting only the latest change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100