Skip to content

x/vulndb: labels not applied when issue is created #50300

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

Closed
julieqiu opened this issue Dec 22, 2021 · 2 comments
Closed

x/vulndb: labels not applied when issue is created #50300

julieqiu opened this issue Dec 22, 2021 · 2 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Milestone

Comments

@julieqiu
Copy link
Member

When an issue is created on the x/vulndb issue tracker, the NeedsTriage label should be applied and it is not. See https://github.com/golang/vulndb/blob/552ce2251f67e44f2553e39b7b878d03d586a8ff/internal/worker/worker.go#L215 and golang/vulndb#145 (as an example).

@gopherbot gopherbot added this to the Unreleased milestone Dec 22, 2021
@julieqiu julieqiu added NeedsFix The path to resolution is known, but the work has not been done. x/vuln labels Dec 22, 2021
@dmitshur
Copy link
Contributor

Is it because the label in x/vulndb doesn't have a space (NeedsTriage),
but in worker.go it does (Labels: []string{"Needs Triage"})?

@julieqiu
Copy link
Member Author

julieqiu commented Jan 5, 2022

Closing since we don't use this label anymore.

@julieqiu julieqiu closed this as completed Jan 5, 2022
@julieqiu julieqiu added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Sep 8, 2022
@golang golang locked and limited conversation to collaborators Sep 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
Status: No status
Development

No branches or pull requests

3 participants