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

[no_severity_nag] Exclude security bugs when nagging triage owner #2536

Merged
merged 5 commits into from
Dec 18, 2024

Conversation

benjaminmah
Copy link
Contributor

Resolves #2505.

Excludes any bugs with a security keyword to avoid nagging the triage owner.

Checklist

  • Type annotations added to new functions
  • Docs added to functions touched in main classes
  • Dry-run produced the expected results
  • The to-be-announced tag added if this is worth announcing

@benjaminmah benjaminmah requested a review from marco-c November 6, 2024 15:59
@benjaminmah
Copy link
Contributor Author

Would it make sense to apply this filter to the other rules that nag the triage owner as well? (p1_no_activity.py, p1_no_assignee.py, etc.)

@marco-c
Copy link
Contributor

marco-c commented Nov 6, 2024

Would it make sense to apply this filter to the other rules that nag the triage owner as well? (p1_no_activity.py, p1_no_assignee.py, etc.)

Which other rules do it? We could ask @mozfreddyb for each of them.

@benjaminmah
Copy link
Contributor Author

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.

configs/rules.json Outdated Show resolved Hide resolved
@suhaibmujahid suhaibmujahid merged commit 038b63c into mozilla:master Dec 18, 2024
2 checks passed
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

Successfully merging this pull request may close these issues.

Stop emailing triage owners about security bugs when they cannot take the next action
3 participants