mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-07-31 20:32:20 +03:00
286574cf39
Contributor guidance contradicted itself in four places (found in the #8084 review): - pull_request_template.md + CONTRIBUTING.md asked contributors to run the FULL unit suite + coverage gate locally, while the maintainer's stated golden path (#8273/#8329) is: focused tests for the change locally; full suite, coverage, and build are CI's job. On 16GB hosts the full local chain has saturated machines (#8084 incident report). - GEMINI.md demanded coverage >= 75/75/75/70 while the official CI gate is 60/60/60/60 (quality-baseline ratchet on top). - AGENTS.md fork workflow said to branch from upstream/main; the default branch is the active release/vX.Y.Z line (main only receives release squash-merges). Also makes the #8084 CI direction explicit in the public ROADMAP: lane consolidation (3.8.51), one CI policy for release/** and main (3.8.52), full-regression authority -> merge queue after TIA shadow evidence (3.8.54), preview-artifact + build-once rehearsal inside the 3.8.58 dry-run. Refs #8329 Refs #8084
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
## Summary
|
|
|
|
- Describe the user-facing or operational change.
|
|
|
|
## Related Issues
|
|
|
|
- Closes #
|
|
- Related to #
|
|
|
|
## Validation
|
|
|
|
Run only the focused loop for what you changed — the full unit suite, Vitest, the
|
|
60% coverage gate, and the production build all run in CI on this PR (#8329):
|
|
|
|
- [ ] Focused tests for the change: `node --import tsx/esm --test tests/unit/<file>.test.ts`
|
|
- [ ] `npm run lint`
|
|
- [ ] Production-code changes include a new or updated automated test in this PR
|
|
- [ ] SonarQube PR analysis is green or any remaining issues are explicitly documented below
|
|
|
|
## Tests Added Or Updated
|
|
|
|
- List every changed or added automated test file.
|
|
- If no production code changed, state that here.
|
|
|
|
## Coverage Notes
|
|
|
|
- If this PR changes `src/`, `open-sse/`, `electron/`, or `bin/`, explain which tests cover the change.
|
|
- If coverage moved down in any touched file, explain why and what follow-up task will recover it.
|
|
|
|
## Reviewer Notes
|
|
|
|
- Call out any risky areas, migrations, feature flags, or manual validation that reviewers should know about. |