-
Notifications
You must be signed in to change notification settings - Fork 68
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
[no_severity_nag] Exclude security bugs when nagging triage owner #2536
base: master
Are you sure you want to change the base?
Conversation
Would it make sense to apply this filter to the other rules that nag the triage owner as well? ( |
Which other rules do it? We could ask @mozfreddyb for each of them. |
Looking through the BugBot Wiki, the following are rules that NAG the triage owner: There are other rules that NEEDINFO the triage owner, however. |
@@ -73,6 +74,8 @@ def handle_bug(self, bug, data): | |||
# check if the product::component is in the list | |||
utils.check_product_component(self.components_skiplist, bug) | |||
or utils.get_last_no_bot_comment_date(bug) > self.activity_date | |||
or any(keyword in SECURITY_KEYWORDS for keyword in bug["keywords"]) | |||
or bug["groups"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do any("security" in group for group in bug["groups"])
so we only exclude security bugs and not bugs that are confidential
or any(keyword in SECURITY_KEYWORDS for keyword in bug["keywords"]) | ||
or bug["groups"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could have this in the query directly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How does this look? 55a1b1f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could instead add it as a configuration, and it will be added to the query:
Line 452 in a8b33be
"sec": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate on this, I'm a little confused on what you mean. Do you mean adding a new "sec": false
configuration under no_severity_nag
and then using that as a condition on whether or not to include the security bugs in the params?
"f34": "bug_group", | ||
"o34": "substring", | ||
"v34": "security", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #2536 (comment)
Resolves #2505.
Excludes any bugs with a security keyword to avoid nagging the triage owner.
Checklist
to-be-announced
tag added if this is worth announcing