You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e12d41c
Browse filesBrowse the repository at this point in the historyBrowse files
The engine runs health checks on every analysis, full or incremental, and
writes health_report.json beside the graph it produced. Nothing kept it:
sync deleted the file instead of installing the fresh one, and review never
uploaded it. The only surviving copy was inside the Actions cache, which
has no download API, so neither the extension nor the webview could read
health information at all. It has been that way since the v2 rewrite in
474d40a, which removed the file as a v1 leftover without noticing that the
engine still produced it.
Sync now installs the report it just generated, and removes a stale one
when a run produced none, matching how the other optional artifacts are
handled. Review ships it in the artifact next to the analyses.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,9 +60,10 @@ The uploaded artifact holds both sides of the comparison, so a reader can reprod
60
60
|---|---|
61
61
| `analysis.json` | the head analysis, at `head_sha` |
62
62
| `base_analysis.json` | the analysis it was compared against, at `merge_base_sha` |
63
-
| `metadata.json` | both SHAs, `merge_base_resolved`, `seed_source`, `chain_depth`, PR number |
63
+
| `health_report.json` | the head's health findings, when the engine produced any |
64
+
| `metadata.json` | which commits those graphs describe — see [the field list](docs/COMMIT_STRATEGY.md#names) |
64
65
65
-
Artifacts are kept 30 days. Reading the default branch's committed baseline instead of `base_analysis.json` would drift from the merge base in exactly the way described above.
66
+
The action requests 30-day retention; a repository or organisation policy can shorten it, so treat an artifact's own `expired` flag as the truth rather than any fixed window. Reading the default branch's committed baseline instead of `base_analysis.json` would drift from the merge base in exactly the way described above.
66
67
67
68
### Reused analysis
68
69
@@ -127,8 +128,9 @@ Sync mode commits only Core's persisted incremental-analysis state under `.codeb
127
128
- `static_analysis.pkl`
128
129
- `static_analysis.sha`
129
130
- `codeboarding_version.json`when emitted by Core
131
+
- `health/health_report.json`
130
132
131
-
It does **not** render or commit architecture Markdown. Existing v1-generated `.codeboarding/*.md` and `docs/development/architecture.md` files carrying CodeBoarding's generated badge, plus `.codeboarding/health/health_report.json`, are removed on the first v2 sync. Hand-written Markdown and user-authored CodeBoarding configuration are preserved.
133
+
It does **not** render or commit architecture Markdown. Existing v1-generated `.codeboarding/*.md` and `docs/development/architecture.md` files carrying CodeBoarding's generated badgeare removed on the first v2 sync. Hand-written Markdown and user-authored CodeBoarding configuration, including `health/health_config.json` and `health/.healthignore`, are preserved.
0 commit comments