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 6a43d14
Browse filesBrowse the repository at this point in the historyBrowse files
fix(review): keep reviews 14 days and base graphs 30 (#93)
The review artifact is the dominant storage cost, being the one kept for
weeks, so it drops from 30 days to 14. Base graphs drop from 60 to 30,
which still leaves a 16-day window in which a base is reused rather than
republished. Modelled at the largest repository we have, that is roughly
3,700 analyses a month within half a Team allowance, against 1,850 before.
The renewal threshold moves with the review retention, because it has to:
a review references a base by id for its whole life, so a base with less
than that remaining is renewed. Ten days against a fourteen-day review
would leave a reference dangling for four. A test now fails if the two
drift apart, since nothing else would notice.
What a pull request open longer than fourteen days loses is the rendered
analysis, until someone asks for it again. That costs one incremental over
the pull request: the base graph is kept longer and needs no re-analysis.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,7 +88,7 @@ Every bundle the action publishes carries a `metadata.json` with a `kind` of
88
88
`review`, `base` or `warmstart`. Check it rather than inferring from the
89
89
payload: a base bundle is otherwise indistinguishable from a head one.
90
90
91
-
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.
91
+
The action requests 14-day retention for it; a repository or organisation policy can shorten that, so treat an artifact's own `expired` flag as the truth rather than any fixed window. When a pull request outlives its review artifact, `/codeboarding` regenerates it at the cost of one incremental over the pull request — the base graph is kept longer and does not need re-analyzing.
Copy file name to clipboardExpand all lines: docs/COMMIT_STRATEGY.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ cache was free. Retention is the lever — see below.
27
27
28
28
| Artifact | Contents | Retention | Read by |
29
29
|---|---|---|---|
30
-
|`codeboarding-review-<run>-<attempt>`|`analysis.json`, `health_report.json`, `metadata.json`|30 days | the webview, humans |
30
+
|`codeboarding-review-<run>-<attempt>`|`analysis.json`, `health_report.json`, `metadata.json`|14 days | the webview, humans |
31
31
|`codeboarding-base-<cfg>-<merge_base>`| the merge base's own analysis | 30 days, renewed while still referenced | any later review forking from that commit |
32
32
|`codeboarding-warmstart-<cfg>-pr<N>`| the working directory: graph, pickle, fingerprint, gate |**1 day**, configurable | only the next run of that pull request |
33
33
@@ -71,9 +71,13 @@ that commit has a different merge base.
71
71
Artifacts are charged by size × time, so the three windows are set by what reads
72
72
them:
73
73
74
-
-**30 days** for the review artifact — a reader may come back to a pull request.
75
-
-**Repository default** for a base graph — it must outlive every review artifact
76
-
that names it.
74
+
-**14 days** for the review artifact — the dominant cost, since it is the one
75
+
kept for weeks. A pull request open longer loses its rendered analysis until
76
+
someone asks for it again, which costs one incremental over the pull request:
77
+
the base graph is still published, so nothing re-analyzes the base.
78
+
-**30 days** for a base graph, which must outlive every review that names it.
79
+
The renewal threshold is the review's own retention, so the surplus — 16 days
80
+
here — is how long a base is reused before being republished.
77
81
-**1 day** for the warm-start bundle, since only the next run reads it. This is
78
82
`warmstart_retention_days` if a repository wants longer. It behaves like the
79
83
old cache eviction: a pull request left alone longer than the window
0 commit comments