fix(health): accept glob alias in health-rules and correct stale docs#463
Closed
RaghavChamadiya wants to merge 3 commits into
Closed
fix(health): accept glob alias in health-rules and correct stale docs#463RaghavChamadiya wants to merge 3 commits into
RaghavChamadiya wants to merge 3 commits into
Conversation
- config.py: accept "glob" (and keep "path_glob") as aliases for the canonical "path" key in .repowise/health-rules.json rules. Both doc examples showed "glob", which the parser silently ignored, so configs copied from the docs never applied; now they work, and the examples use the canonical key with the aliases documented. Test added. - analysis/health/README.md: "twelve biomarkers" was stale; the registry holds 26, plus 3 additive governance findings. - docs/architecture/code-health.md: add the 6 biomarker files missing from the layer file tree; drop the stale "no PR-mode delta in v1" non-goal (the change_risk package and repowise risk shipped). - docs/CODE_HEALTH.md: hotspot health averages over files the git layer classifies as hotspots, not a fixed top-25% slice. No behavior change other than the new key aliases.
Graph-aware scanning, function-level reachability (per-ecosystem coverage), VEX export, PCI-DSS and SOC 2 compliance reporting, signed Slack-compatible security webhooks, and the audit-event stream are now live on the hosted platform; matrix rows and section 5 prose updated to match.
Slack/Teams alerting now covers engineering signals (hotspot drift, bus-factor risk, health decline, decision staleness) alongside security events, and the engineering leader dashboard is GA on hosted (Teams).
|
✅ Health: 7.6 (unchanged)
🔥 Hotspots touched (2)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-06-12 08:28 UTC |
Member
Author
|
Superseded: this exact changeset already landed on main inside #458 (its squash includes the glob-alias commit). All five files are byte-identical between this branch and main, so closing. |
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
1 participant
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.
What
Integrity sweep over the code-health configuration surface and docs. One behavior change, the rest documentation corrections.
Config fix
Both doc examples for
.repowise/health-rules.jsonshowed a"glob"key on rule entries, but the parser only acceptedpath/path_glob, so any per-path override copied from the docs was silently ignored.globis now accepted as an alias (with a test), the examples use the canonicalpathkey, and the aliases are documented.Docs corrections
analysis/health/README.mdclaimed "twelve biomarkers"; the registry holds 26, plus 3 governance findings written by a separate additive pass.docs/architecture/code-health.mdwas missing 6 of the biomarker files from the layer's file tree (low_cohesion, god_class, coverage_gradient, prior_defect, large_assertion_block, duplicated_assertion_block), and still listed "no PR-mode delta in v1" as a non-goal even though thechange_riskpackage andrepowise riskshipped.docs/CODE_HEALTH.mddescribed hotspot health as an average over "the top-25% hotspot files"; it actually averages over the files the git layer classifies as hotspots (churn percentile plus minimum-activity floors).Tests
tests/unit/health/test_health_config.pygains an alias-acceptance test; the suite passes.