CVE Feed: Sort Markdown Table from most recent to least recently announced CVE

kubernetes / sig-security

Process documentation, non-code deliverables, and miscellaneous artifacts of Kubernetes SIG Security

Apache License 2.0

161 stars 53 forks source link

CVE Feed: Sort Markdown Table from most recent to least recently announced CVE #73

Closed PushkarJ closed 1 year ago

PushkarJ commented 1 year ago

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 markdown

k8s-triage-robot commented 1 year ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

PushkarJ commented 1 year ago

/remove-lifecycle stale

PushkarJ commented 1 year ago

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.

PushkarJ commented 1 year ago

/close

(As per last comment)

k8s-ci-robot commented 1 year ago

@PushkarJ: Closing this issue.

In response to [this](https://github.com/kubernetes/sig-security/issues/73#issuecomment-1498335928): >/close > >(As per last comment) Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.