Repository navigation
v0.5.0 — developer-workflow integration (composite action, baseline gate, honest CI semantics) - #5
Merged
Merged
Conversation
… .qoder-handover) Applies the preserved patch from the v0.3.0 takeover: the combined GitHub issue document now groups js-exception/console-error findings by fault cluster (aggregated status + collapsed per-page member detail with full evidence), while other finding types render standalone as before. Baseline for dedicated cluster-markdown tests in this release.
The quarantined v0.3.0 change shipped without tests; this adds a 5-case suite: grouping, standalone resource types, exactly-once id traceability, aggregated repro numbers + cluster id, and back-compat for cluster-less results.
…flows - .github/actions/reprocase-scan: pinned-ref install (github tarball), same-runner scan (localhost test servers work), explicit exit-code semantics (0/1/2 + ::error annotations for environment problems), baseline compare gate with first-run grace, privacy-stripped artifact (traces deleted before upload), minimal permissions, no third-party keys - scan --detection-window-ms: CI-friendly async budget flag (verified end-to-end against the audit site) - action.yml inputs: url, config, compare-with, fail-on, fail-on-new, max-pages, detection-window-ms, report-name, node-version, reprocase-ref
docs/github-actions.md: quick start, inputs/outputs tables, exit-code semantics (environment errors never impersonate site verdicts), baseline gating flow, PR-comment security stance (two-workflow pattern documented, no token to untrusted PR code), privacy policy. READMEs link it (en+zh). docs guard now enforces --detection-window-ms documentation.
…obal install npm global mode strips devDependencies, so 'npm i -g github:...' failed at prepare (tsc + @types/node missing). The action now clones the pinned ref, runs npm ci (dev deps included), builds, and installs the built package globally. Found by the real external-repo CI run.
… components, CI integration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.github/actions/reprocase-scan: third-party CI integration with pinned-ref install (clone → npm ci → build → global install), same-runner scans (localhost works), explicit 0/1/2 exit semantics with environment-error annotations, baseline new-faults gate (first-run grace, coverage-aware), privacy-stripped artifacts (traces deleted before upload).scan --detection-window-ms: CI-friendly async observation budget.External acceptance
Real integration repository reprocase-actions-demo: clean scan green, incident commit red (2 verified faults + compare gate 2 new findings), fix commit green, scanner-environment error honestly reported (exit 2 + verdict=error asserted).
Verification
142/142 tests, npm audit 0, four-OS CI matrix, docs-CLI consistency guard, package-lock consistency check.