-
Notifications
You must be signed in to change notification settings - Fork 62
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
CVE Feed: Sort Markdown Table from most recent to least recently announced CVE #73
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
With limitation or additional complexity of sorting markdown tables with hugo and existing sequential assignment of issues for CVEs, I am leaning towards letting the markdown table sort based on Issue number as is happening today automatically. Will keep this open for now, so folks can chime in and close in a week or so if there are no more concerns. |
/close (As per last comment) |
@PushkarJ: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Description
To have the most recently
announced
CVE to be at the top of the field will allow everyone to know which was the most recent that they should be aware of. Currently, this is somewhat already happening with table being sorted based on column "Github Issue"Details
JSON: No changes needed apart from #63
Markdown: Use the timestamp that depicts when the issue was "closed" i.e. from
closed_at
timestamp from Github REST API output: https://docs.github.com/en/rest/issues/issues#get-an-issue . Open to discuss if we want timestamp column named "Fixed On" visible or invisible in markdownThe text was updated successfully, but these errors were encountered: