Feature Summary
Add Git change indicators to parent folders in the Git Changes tree when any descendant file or folder contains changes.
Problem or Use Case
Currently, changed files show indicators, but parent folders can appear unchanged when the actual changes are nested deeper inside. This makes collapsed folders harder to scan because I have to expand them to know whether they contain changed files.
It would be helpful if emdash could show that a parent folder contains changes even when the changed files are inside child folders.
Proposed Solution
Propagate Git change state upward in the Git Changes tree.
Expected behavior:
- If a folder contains changed descendants at any depth, the folder shows a change indicator.
- The indicator remains visible when the folder is collapsed.
- Existing file-level and child-folder indicators continue to work.
- The styling should match the existing Git Changes UI.
- Folders containing descendant changes should use the existing orange change indicator style.
Alternatives Considered
The current workaround is to manually expand folders to check whether they contain changed files. This works, but it is slower when changes are nested across multiple folders.
Additional Context
This would make the Git Changes tree easier to scan, especially for projects with deeply nested files or many changed files across different folders.
Feature Summary
Add Git change indicators to parent folders in the Git Changes tree when any descendant file or folder contains changes.
Problem or Use Case
Currently, changed files show indicators, but parent folders can appear unchanged when the actual changes are nested deeper inside. This makes collapsed folders harder to scan because I have to expand them to know whether they contain changed files.
It would be helpful if emdash could show that a parent folder contains changes even when the changed files are inside child folders.
Proposed Solution
Propagate Git change state upward in the Git Changes tree.
Expected behavior:
Alternatives Considered
The current workaround is to manually expand folders to check whether they contain changed files. This works, but it is slower when changes are nested across multiple folders.
Additional Context
This would make the Git Changes tree easier to scan, especially for projects with deeply nested files or many changed files across different folders.