Closed dalehenries closed 9 months ago
This issue is currently awaiting triage.
If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Welcome @dalehenries!
It looks like this is your first PR to kubernetes/kube-state-metrics 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/kube-state-metrics has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dalehenries, mrueg
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Thanks for your contribution @dalehenries !
Thank you for your work here, @dalehenries!
The OpenSSF practices are something we can surely utilize within the repository. However, to better visualize and trigger the checks (IIUC these are only presented as raw json
currently), can we add an action for it here as well?
What this PR does / why we need it: Adds the OpenSSF Scorecard to the README
SecuritySlam
Which issue(s) this PR fixes: Related to #2274