Description
For a merged pull request, buildDecaySubline (used in PRTimeDecayChart) returns how many days have passed since merge. The string was built as ${projection.daysSinceMerge.toFixed(1)} days since merge, which reads incorrectly at 1.0 (e.g. “1.0 days since merge”). It should use {t} day(s) since merge (e.g. 1.0 day(s) since merge, 2.0 day(s) since merge).
Steps to Reproduce
- Open
/miners/pr?repo=...&number=... for a PR that is merged and still inside the decay lookback window.
- Find the Time Decay card and read the subline under the “Time Decay” title (not the chart axis).
- When
daysSinceMerge is 1 (shown as 1.0 via toFixed(1)), read the noun after the number.
Expected Behavior
- Subline uses
{t} day(s) since merge (e.g. 1.0 day(s) since merge, 2.0 day(s) since merge).
Actual Behavior
buildDecaySubline always appended “days since merge” (e.g. “1.0 days since merge”).
Environment
- Browser: any.
- OS: any.
- URL:
/miners/pr?repo=...&number=... (merged PR).
Additional Context

Description
For a merged pull request,
buildDecaySubline(used inPRTimeDecayChart) returns how many days have passed since merge. The string was built as${projection.daysSinceMerge.toFixed(1)} days since merge, which reads incorrectly at 1.0 (e.g. “1.0 days since merge”). It should use{t} day(s) since merge(e.g. 1.0 day(s) since merge, 2.0 day(s) since merge).Steps to Reproduce
/miners/pr?repo=...&number=...for a PR that is merged and still inside the decay lookback window.daysSinceMergeis 1 (shown as1.0viatoFixed(1)), read the noun after the number.Expected Behavior
{t} day(s) since merge(e.g. 1.0 day(s) since merge, 2.0 day(s) since merge).Actual Behavior
buildDecaySublinealways appended “days since merge” (e.g. “1.0 days since merge”).Environment
/miners/pr?repo=...&number=...(merged PR).Additional Context