-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Colorize status badge #4286
Colorize status badge #4286
Conversation
@daviddossett what do you think of the colored status? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Open to this in principle but there are some theming issues to iron out:
CleanShot.2022-12-05.at.10.03.21.mp4
- I believe the color should not be static for all themes. Rather, it should feel like part of that theme. That's why I used
badge.background
if memory serves. The challenge here is that people have strong associations with the GitHub colors. So we need to balance it feeling like the colors fit with the current theme with that association. Open to ideas here. - Some themes don't seem to render a background color at all
This is only the case for high contrast themes and on purpose. I added a border in my latest commit.
Theme authors can change the color using Furthermore, I fixed some issues with the font color on light themes. |
…st-github into colorize-status-badge
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR, this looks very nice. I have just two small comments about reusing colors.
package.json
Outdated
"dark": "#238636", | ||
"light": "#238636", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's base this off of the issues.open
color so we don't have two slightly different open colors.
"dark": "#238636", | |
"light": "#238636", | |
"dark": "issues.open", | |
"light": "issues.open", |
package.json
Outdated
"dark": "#da3633", | ||
"light": "#da3633", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as for issues.open
:
"dark": "#da3633", | |
"light": "#da3633", | |
"dark": "issues.closed", | |
"light": "issues.closed", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I accepted my suggestions so that the change can be merged. The colors can still be changed before release if there is disagreement.
Thanks for taking this PR! I'm ok with the changed colors. |
Indicate the status of a PR with different colors and icons. One can now see immediately weither a PR is closed, merged, open or a draft.
Note that you were against colored status badges in #535. However, I think that they are looking substantially different from buttons now and also have icons in them:
In particular, the differences to buttons are:
Furthermore, I think that it is clear from the context around them that they are status badges and not buttons.
Another concern was that the previous implementation did not respect theme settings. I added the background colors to the color contribution point.