Skip to content
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

Closed
Tracked by #1
PushkarJ opened this issue Nov 22, 2022 · 5 comments
Closed
Tracked by #1

Comments

@PushkarJ
Copy link
Member

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

@PushkarJ PushkarJ changed the title Sort Markdown Table from most recent to least recent CVE CVE Feed: Sort Markdown Table from most recent to least recent CVE Nov 22, 2022
@PushkarJ PushkarJ changed the title CVE Feed: Sort Markdown Table from most recent to least recent CVE CVE Feed: Sort Markdown Table from most recent to least recently announced CVE Nov 22, 2022
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2023
@PushkarJ
Copy link
Member Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 20, 2023
@PushkarJ
Copy link
Member Author

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
Copy link
Member Author

PushkarJ commented Apr 6, 2023

/close

(As per last comment)

@k8s-ci-robot
Copy link
Contributor

@PushkarJ: Closing this issue.

In response to this:

/close

(As per last comment)

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants