Configure the three Core :: Machine Learning components for automatic triage - #3015
Merged
suhaibmujahid merged 1 commit intoSep 4, 2026
Merged
Conversation
… triage so Smart Window bugs reach the agent the hour they are filed rather than whenever someone remembers to ask These are the first Core components on the list, and the first whose names contain a colon, neither of which the query construction cares about since each pair already gets its own AND group. The agent's TRIAGE_SCOPE routes all three to #smart-window-bug-triage; channel_for fails closed, so this needs the bugbug side deployed first or the three pairs get unattended triage with nobody told.
suhaibmujahid
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The agent gets channels for these three in mozilla/bugbug#6789, so the hourly rule can start sending it Smart Window bugs. They are the first Core pairs and the first component names containing a colon, neither of which the query construction cares about.
That must deploy first:
channel_forfails closed, so a pair here ahead of the agent gets unattended triage with nobody told.