-
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
Web Compatibility bugs do not get release management updates #2533
Comments
The Lines 37 to 56 in 4afbef8
I will include it, which will enable all BugBot rules on the |
Yes - we disabled it on purpose because a lot of the lints (disparaging severity/priority, etc) don't apply to our components in a way that makes sense. If we can only enable specific rules, like the regression-helper, that'd be perfect. |
If you can do the specific rules then that would be ok for relman. |
Please add anything that you need. Our motivation for disabling rules was simply to reduce bugmail traffic for things we don't care about - but I'd be more than happy to just ignore/dismiss nudges. :) |
@denschub what do you think of doing this: enable everything, then when you see something that should be disabled we disable it. |
Works for me. :) |
The webcompat team uses bugs in the
Web Compatibility
product to track bugs. These may include regressions.Example:
https://bugzilla.mozilla.org/show_bug.cgi?id=1929199 has a regressor.
However, bugbot did not update the release tracking and it did not add a need-info on the regressor assignee.
The text was updated successfully, but these errors were encountered: