-
Notifications
You must be signed in to change notification settings - Fork 48
docs: add more readme flair #1295
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
base: main
Are you sure you want to change the base?
Conversation
We were only using the minimum amount of flair.  Signed-off-by: Alex Lowe <[email protected]>
Signed-off-by: Alex Lowe <[email protected]>
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.
And in the proper spirit of the 90s, it's like I'm looking at the site footer on Geocities.
I'm going to be the devil's advocate, assuming we want this to become a pattern across our projects. It's not what I had in mind with the README model.
Do we need all of these? There are several that from what I can tell don't provide a variable status. They feel like TF2 hats.
I think there ought to be a rational order to these, at minimum. Something like license > builds > security checks > build checks.
There's no way that download count is an honest metric, right?
upils
left a comment
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 agree with @medubelko. It is shiny and fun but it is becoming a bit too much and might be counterproductive by making it hard to find the desired information.
Should we write a small policy with what badges should be / could be / should not be present? (and where they should be?)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Make sure to clean the package cache layer when an underlying layer is cleaned.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Some of these are also causing frequent lint CI failures
Signed-off-by: Alex Lowe <[email protected]>
Co-authored-by: JJ Coldiron <[email protected]>
Signed-off-by: Alex Lowe <[email protected]>
| [![GitHub License][license-badge]][license-link] | ||
| [][pypi] | ||
| [][pypi] | ||
|  |
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.
While this isn't as readily available information, I'm not sure about how useful it actually is. Given that we just run make setup and go about our day, the exact Python versions in use aren't that important to surface.
Also, why is this one formatted differently from the rest (doesn't begin with [)?
| [![Codecov Status][codecov-badge]][codecov-status] | ||
| [![Code Style][ruff-badge]][ruff-site] | ||
| [![Canonical Starcraft][starcraft-badge]][canonical-link] | ||
| [![GitHub License][license-badge]][license-link] |
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 can understand wanting to add this (being GPL is cool!), but this information can already be found in multiple other places, particularly on the sidebar of the repository.
I'm on the side of "let's delete it", but if others have a strong FOSS spirit and strongly want to keep it, I'm okay with that too.
| [![Code Style][ruff-badge]][ruff-site] | ||
| [![Canonical Starcraft][starcraft-badge]][canonical-link] | ||
| [![GitHub License][license-badge]][license-link] | ||
| [][pypi] |
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 don't think this is helpful information, it's already on the sidebar.
| [![Canonical Starcraft][starcraft-badge]][canonical-link] | ||
| [![GitHub License][license-badge]][license-link] | ||
| [][pypi] | ||
| [][pypi] |
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.
goofy
| [][pypi] | ||
| [][pypi] | ||
|  | ||
| [![QA][qa-badge]][qa-link] |
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.
nit: I wish this said "Tests", but that would have to be fixed by renaming the workflow file.
| [][pypi] | ||
|  | ||
| [![QA][qa-badge]][qa-link] | ||
| [![TICS][tics-badge]][tics-link] |
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.
This is only useful to us, and we have our own ways of checking the TICS status. I don't care for this badge.
| [![QA][qa-badge]][qa-link] | ||
| [![TICS][tics-badge]][tics-link] | ||
| [![GitHub commits since latest release][commits-badge]][releases-link] | ||
| [![GitHub Release Date][release-date-badge]][releases-link] |
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.
This is already on the sidebar next to the version
| [![Documentation Status][rtd-badge]][rtd-latest] | ||
| [![Codecov Status][codecov-badge]][codecov-status] | ||
| [![Code Style][ruff-badge]][ruff-site] | ||
| [![Canonical Starcraft][starcraft-badge]][canonical-link] |
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 actually love this. Should we talk to design about somehow getting an even prettier badge?
We were only using the minimum amount of flair.
Rendered: https://github.com/canonical/craft-parts/blob/work/more-flair/README.md
make lint && make test?docs/reference/changelog.rst)?