fix(web): clarify health trend score changes#457
Merged
RaghavChamadiya merged 1 commit intoJun 12, 2026
Conversation
|
✅ Health: 7.7 (unchanged) 🔥 Hotspot touched (1)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-06-11 14:50 UTC |
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
Fixes #452.
Why
The trend page section listed files whose health scores changed most between the latest snapshots, but the heading said "Files that moved most since last index." That read like file moves or renames, which is not what the table represents.
The new heading, "Largest score changes since last index," matches the data shown in the table: before score, after score, and delta.
Scope
This is a copy-only web UI change:
Verification
npm.cmd cinpm.cmd run type-check --workspace packages/webgit diff --check