Skip to content

[WIP] Add front-end triage automation for Messaging System - #6600

Open
dmose wants to merge 2 commits into
mozilla:masterfrom
dmose:omc-automation
Open

[WIP] Add front-end triage automation for Messaging System#6600
dmose wants to merge 2 commits into
mozilla:masterfrom
dmose:omc-automation

Conversation

@dmose

@dmose dmose commented Aug 17, 2026

Copy link
Copy Markdown
Member

This sets up the front-end triage agent to also work with the Firefox :: Messaging System component.

Before this gets merged, three things need to happen:

[ ] The OMC team Technical Point-Of-Contact should reach out to coordinate with @msujaws
[ ] If the OMC team has decided that they want a Slack channel other than #omc-triage, this PR needs updating.
[ ] Remove [WIP] from the PR title
[ ] At least @msujaws should review. Jared, I believe this includes all the changes you suggested. I have run the changed agent using docker compose to execute the front end triage agent on the command line and it seemed to behave reasonably. I haven't had time to test hackbot driving the agent.

Add the desktop Messaging System (about:welcome, feature callouts, Spotlight,
Infobars) as a triaged area: a SLACK_CHANNELS entry for
"Firefox :: Messaging System", the matching README routing row and component
list entry, and the source locations (browser/components/asrouter/,
browser/components/aboutwelcome/, toolkit/components/messaging-system/) in the
triage rules so localization has somewhere to look.
@dmose
dmose requested a review from a team as a code owner August 17, 2026 00:24
Copilot AI lite review requested due to automatic review settings August 17, 2026 00:24

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR extends the existing frontend-triage agent’s component-to-Slack routing to include the Firefox :: Messaging System component, so auto-applied triage runs can notify the appropriate team channel.

Changes:

  • Add Firefox :: Messaging System#omc-triage routing in the agent config.
  • Add/extend unit test coverage to assert correct routing for the new component.
  • Update README and Hackbot rules documentation to include the Messaging System scope and source-area pointers.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
agents/frontend-triage/tests/test_notify.py Adds an assertion that Firefox :: Messaging System routes to #omc-triage.
agents/frontend-triage/README.md Documents Messaging System as in-scope and adds it to the routing table.
agents/frontend-triage/hackbot_agents/frontend_triage/rules/frontend-triage.md Updates the rules to include Messaging System and related source areas.
agents/frontend-triage/hackbot_agents/frontend_triage/config.py Adds the Firefox :: Messaging System entry to SLACK_CHANNELS.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines 40 to +44
(`.sys.mjs`, IDL, C++); the installer under `browser/installer/windows/nsis/`
(NSIS `.nsi`/`.nsh`). Find the module, the markup or layout, and any relevant pref
(often `modules/libpref/init/all.js`, or `app.update.*` for the updater) that
governs the behaviour. Use the `investigator` subagent for deep searches.
(NSIS `.nsi`/`.nsh`), Messaging System under `browser/components/asrouter/`,
`browser/components/aboutwelcome/`, `toolkit/components/messaging-system/`
(JS/JSM, CSS, XUL/HTML, JSON, JSON Schema). Find the module, the markup or layout,
and any relevant pref (often `modules/libpref/init/all.js`, or `app.update.*`
@crythms
crythms requested a review from msujaws August 17, 2026 17:24
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.

2 participants