benmichael/gods-eye-view
1
0 Fork 0
mirror of https://github.com/bilawalsidhu/gods-eye-view.git synced 2026-11-04 02:14:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1196 from HyperionBurn/docs/qa-gate-npm-alias-list

Browse Source 
docs: list every npm alias for the qa gates
This commit is contained in:
Sameh Khamis authored and GitHub committed 2026-10-17 12:02:40 -07:00
2 parents 73aec2e6b2 7828f69038
commit 710f2e9710
1 file changed
+9 -7
Download Patch File Download Diff File Expand all files Collapse all files
CONTRIBUTING.md
+9 -7
View File
@@ -54,8 +54,9 @@ head -40 scripts/qa-radio.mjs # what this runnable gate proves and how to run i
Runnable gate entrypoints document what they assert and how to invoke them. Runnable gate entrypoints document what they assert and how to invoke them.
Most need a dev server; some also need a specific provider key or port. Follow Most need a dev server; some also need a specific provider key or port. Follow
the entrypoint's header rather than assuming every matching file accepts the the entrypoint's header rather than assuming every matching file accepts the
same arguments. Only a couple (`qa:map-source-tray`, `qa:transit`) have an same arguments. Five have an `npm run` alias: `qa:map-source-tray`,
`npm run` alias. `qa:panel-resize`, `qa:street-level`, `qa:street-level:fixtures` and
`qa:transit`.
If you aren't sure which gate covers your change, search `docs/CURRENT-STATE.md` If you aren't sure which gate covers your change, search `docs/CURRENT-STATE.md`
for the feature: it names the gate for many of them, and it's the authoritative for the feature: it names the gate for many of them, and it's the authoritative
@@ -63,12 +64,13 @@ runtime reference either way. `scripts/qa-l9-matrix.mjs` aggregates the broader
release-candidate checks and selected harnesses; it does not replace the focused release-candidate checks and selected harnesses; it does not replace the focused
gate for the feature you changed. gate for the feature you changed.
> **CI does not cover this for you.** The workflow runs the setup policy > **CI covers only two of these for you.** The workflow runs the setup policy
> checks, the formatting and package-boundary checks, the unit suite and the > checks, the formatting and package-boundary checks, the unit suite and the
> production build, plus a Windows onboarding job. It runs neither > production build, plus a Windows onboarding job, and against the built preview
> `npm run test:track` nor any `qa-*.mjs` gate — both need a live dev server > it runs `qa:street-level:fixtures` and `qa:panel-resize`. It does not run
> and a browser. Include the applicable local run in your PR's validation > `npm run test:track` or any other `qa-*.mjs` gate — those need a live dev
> evidence. > server and a browser. Include the applicable local run in your PR's
> validation evidence.
## Share-link layer tokens ## Share-link layer tokens