mozilla / mozilla/experimenter
Warn on missing/mismatched desktop message triggers across branches
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 229
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 212
Description
If any branch configures a desktop message trigger, we should detect and warn if any other branches are either missing or have different triggers so that we don't wreck the consistency of the exposure signals.
┆Issue is synchronized with this Jira Task
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating the validation entry point for experiment branch configuration and existing tests for desktop message triggers; done means inconsistent or missing triggers produce warnings while consistent branch configurations remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100