Repository navigation
Validate .standard color palette for source control badges #6
Description
Proposed mapping:
- modified →
.orange - added →
.green - untracked →
.green - deleted →
.red - conflict →
.red - renamed →
.blue - submodule →
.secondary - typechange →
.secondary
Needs validation — do these provide enough visual distinction? Especially added vs. untracked (both green), and deleted vs. conflict (both red).
Available SwiftUI system colors
| Color | Used for |
|---|---|
.black |
— |
.blue |
renamed |
.brown |
— |
.clear |
— |
.cyan |
— |
.gray |
— |
.green |
added, untracked |
.indigo |
— |
.mint |
— |
.orange |
modified |
.pink |
— |
.purple |
— |
.red |
deleted, conflict |
.teal |
— |
.white |
— |
.yellow |
— |
.primary |
— |
.secondary |
submodule, typechange |
.accentColor |
— |
Unused: .black, .brown, .clear, .cyan, .gray, .indigo, .mint, .pink, .purple, .teal, .white, .yellow, .primary, .accentColor
Consider using distinct colors for statuses that currently share (e.g., .mint or .teal for untracked to distinguish from added, .pink for conflict to distinguish from deleted).
Activity