Showcase two of our distinguishing features #2705
Conversation
|
| @@ -3,13 +3,16 @@ | |||
| height="130"> | |||
| </p> | |||
| <p align="center"> | |||
| <a href="https://github.com/badges/shields/graphs/contributors" alt="Contributors"> | |||
There was a problem hiding this comment.
More general comment, but what do you think about grouping the badges in separate buckets vs all back to back? For example we could have one line (or paragraph) for activity related badges (contributors, commits, sponsors, backers), another line for dev/code metrics (build status, code coverage, service test status, lgtm alerts), and another line for the social badges.
There was a problem hiding this comment.
I suppose that does end up taking up a lot more vertical real estate so not crazy about that 🤔 I just get used to locating a badge (like coverage or service tests in particular) in a particular location and was trying to think of a way they wouldn't jump around so much when we add new badges
There was a problem hiding this comment.
We are getting a little bit into https://twitter.com/NikolayTalanov/status/860444084594393088 territory 😁
We could group them into different sections in the readme, like put stuff related to community participation in one place, and stuff related to quality in another. It could be worth having a "maintainers dashboard" in one of the other readme files.
There was a problem hiding this comment.
Ah that gave me a good chuckle. I like the idea of a maintainers view too. The ones I check the most are the coverage and build/service test status so would be nice to have somewhere to find those quickly.
# Conflicts: # README.md
… to brightgreen See examples in #2705 (comment)
Vaguely on topic:
brightgreen.