You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Automatically add "type-security" to pull requests with CVE in news entry #727
Blurb added a new cve option in python/blurb#95, Bedevere can now look for this option in a news entry and add the type-security label to pull requests with a CVE associated.
In the current code all PR classification is based on filenames in the diff. Would it meet the need to add type-security to every PR that touches a file under Misc/NEWS.d/next/Security? If the answer is yes then this is very easy. If the answer is no then it's not hard, the data we need is available at classification time, it just requires building and reworking some plumbing around the classifier.
That would be a decent way to handle this I think! Maybe we can add a double-check in blurb then that anything with .. cve: is in Security? cc @StanFromIreland
Activity
brettcs commentedon Nov 10, 2026
In the current code all PR classification is based on filenames in the diff. Would it meet the need to add
type-securityto every PR that touches a file underMisc/NEWS.d/next/Security? If the answer is yes then this is very easy. If the answer is no then it's not hard, the data we need is available at classification time, it just requires building and reworking some plumbing around the classifier.sethmlarson commentedon Nov 10, 2026
That would be a decent way to handle this I think! Maybe we can add a double-check in
blurbthen that anything with.. cve:is inSecurity? cc @StanFromIrelandStanFromIreland commentedon Nov 10, 2026
That's already partly done, we don't allow
.. cve:in sections other than Security.gh-727: Add `type-security` to PRs with security blurbs (#728)