You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if we should do the same for our issue status badge (PRs will remain the same since they already differentiate between merged/rejected) and curious what others think. I confess I'm still on the fence myself, but think I'm leaning towards changing to purple
The text was updated successfully, but these errors were encountered:
Sounds like sufficient consensus to me, will take a look at implementing later today. Do we think this will be one of those things that'll need a query param for toggling between red/purple in order to satiate those preferring to maintain the red?
GitHub's experience tiers have switched from displaying closed issues as red to purple (e.g. see our own closed issues https://github.com/badges/shields/issues?q=is%3Aissue+is%3Aclosed), ostensibly to avoid categorically connoting the failed/rejected/etc. theme of red.
I'm wondering if we should do the same for our issue status badge (PRs will remain the same since they already differentiate between merged/rejected) and curious what others think. I confess I'm still on the fence myself, but think I'm leaning towards changing to purple
The text was updated successfully, but these errors were encountered: