[rush reporter][R2] Add opt-in controls and the frontend ReporterHost
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- nodejs, typescript
Research direction
First resolve the blocker in issue #5974, then inspect the reporter frontend under apps/rush and the rush.json and experiments.json configuration surfaces. Trace how command-line controls reach ReporterHost/ReporterManager, and verify the acceptance criteria across TTY, non-TTY, and CI inputs, including legacy defaults and actionable failures.
Written by the indexing model from the issue text.
Description
Parent: #5858
Blocked by: #5974
Goal
Create the authoritative frontend reporter host and reversible pre-major activation controls, while preserving legacy output by default.
Scope
- Construct
ReporterHost/ReporterManagerinapps/rushbefore Rush version selection. - Register
--reporter,--output,--log-level,--quiet,--verbose, and--debugthrough the supported command-line surface. - Read reporter configuration and
agentEnvironmentVariablesfromrush.json. - Add an
experiments.jsonopt-in (proposed name:useRushReporter). - Treat either an explicit non-legacy
--reporteror the repository experiment as a deliberate pre-major opt-in; do not enable agent auto-selection yet. - Preserve
RUSH_REPORTER=legacyas the emergency override.
Acceptance criteria
- The frontend owns reporter selection and hands the engine only a typed sink.
- No opt-in produces the current legacy output and behavior.
- Explicit and repository-level opt-ins are deterministic and covered across TTY, non-TTY, and CI inputs.
- Unsupported or contradictory controls fail with an actionable diagnostic.
- Agent detection remains disabled as a default-selection mechanism until R8.
DAG
Unblocks R5 and R6.
Part of #5858.
- Dominant language
- TypeScript
- Stars
- 6.5k
- Forks
- 708
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 48
Contributor guide
No contributing guide indexed for this repository
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.
More from microsoft/rushstack
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in microsoft/rushstack
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dennys-bd/agent-hive#184 ·
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vicharanashala/fln#563 ·