In the Changes view, some current status symbols are not immediately clear:
± for Modified
★ for Untracked
The star is not commonly associated with an untracked file, while ± is difficult to recognize at this size.
The distinction also relies heavily on color, especially Goldenrod and LimeGreen. File statuses should remain identifiable without relying on color alone, improving accessibility for color-blind users.
A consistent letter-based mapping could be:
| Status |
Badge |
| Modified |
M |
| Type changed |
T |
| Added |
A |
| Deleted |
D |
| Renamed |
R |
| Copied |
C |
| Untracked |
U |
| Conflicted |
X |
Existing colors could remain as a secondary indicator, while the badge itself would always identify the status.
For conflicts, the existing detailed markers such as UU, AU, UD, and AA could remain displayed separately.
The main usability issue is with Modified and Untracked files, but applying the same letter-based convention to all statuses would keep the UI consistent.
In the Changes view, some current status symbols are not immediately clear:
±for Modified★for UntrackedThe star is not commonly associated with an untracked file, while
±is difficult to recognize at this size.The distinction also relies heavily on color, especially Goldenrod and LimeGreen. File statuses should remain identifiable without relying on color alone, improving accessibility for color-blind users.
A consistent letter-based mapping could be:
MTADRCUXExisting colors could remain as a secondary indicator, while the badge itself would always identify the status.
For conflicts, the existing detailed markers such as
UU,AU,UD, andAAcould remain displayed separately.The main usability issue is with Modified and Untracked files, but applying the same letter-based convention to all statuses would keep the UI consistent.