-
Notifications
You must be signed in to change notification settings - Fork 532
Conformance Profiles: Badges for Reports #2293
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
Conformance Profiles: Badges for Reports #2293
Conversation
Signed-off-by: Shane Utt <shaneutt@linux.com>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: shaneutt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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 @shaneutt!
1bcb293
to
4881745
Compare
Co-authored-by: Rob Scott <rob.scott87@gmail.com>
/lgtm |
What type of PR is this?
/kind cleanup
/kind documentation
/area conformance
What this PR does / why we need it:
This adds badges for implementations which are reporting conformance. The badges are placed under the organization name on the
implementations.md
page, and multiple badges can be listed if there are multiple projects. This helps us meet more of the graduation criteria for GEP 1709 to graduate the conformance profiles work to standard.For now, these badges are simple and manually managed so that we can just have some display layer to start with. We expect that in the future we'll get tired of this and there will be more iterations to automate this process.
Which issue(s) this PR fixes:
Fixes #2286
Does this PR introduce a user-facing change?: