Add a component_specific model to identify 'general' bugs that should be moved into more specific components#5892
Merged
marco-c merged 1 commit intomozilla:masterfrom Apr 1, 2026
Conversation
… be moved into more specific components
marco-c
commented
Mar 31, 2026
suhaibmujahid
approved these changes
Mar 31, 2026
This was referenced Apr 1, 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.
This is a v1, a better approach would be to have a model that is trained on the output of the normal component model, where the options to learn would be something like:
I'll file a follow-up issue to implement that.
Train on Taskcluster: componentspecific