Skip to content

Point issue references at this repo, not a repo that no longer exists - #939

Merged
ryanbr merged 1 commit into
mainfrom
fix/qualify-upstream-refs-and-cap
Jul 29, 2026
Merged

Point issue references at this repo, not a repo that no longer exists#939
ryanbr merged 1 commit into
mainfrom
fix/qualify-upstream-refs-and-cap

Conversation

@ryanbr

@ryanbr ryanbr commented Jul 29, 2026

Copy link
Copy Markdown
Owner

Comments only — no schema, no behaviour, no stored value.

The problem

The sleep files carried #600 and #690 from the project's pre-fork repo. github.com/NoopApp/noop
404s and this repo is a fork whose parent no longer resolves, so those links were dead — and worse, they
collide with real numbers here:

number in this repo in the sleep comments
#600 feat(ios): Target Strain Reached notification the V2 staging recipe
#690 GET_BODY_LOCATION_AND_STATUS probe — cited correctly by BodyLocationProbe the V2 staging flag

So #690 meant two different things depending on which file you were reading.

Now pointed at this repo

Nothing live pointed at the old repo — checked, because a dead update endpoint would have mattered
more than any comment. UpdateChecker.swift:21 and UpdateCheck.kt:18 both read
api.github.com/repos/ryanbr/noop/releases/latest, and both About links go to github.com/ryanbr/noop.

The two AppChangelog entries mentioning NoopApp are deliberately left alone. They are the shipped
release notes for the version that made that change; rewriting them would falsify the record rather than
correct it.

Also: the Oura sidecar cap

ReportReviewGate described the Tier-B sidecars as "each up to the 20 MB cap". Both dumps enforce
maxBytes = 25 * 1024 * 1024. Relevant to #937, which adds a third sidecar and should not copy a wrong
number.

Verification

Comments only — verified mechanically, zero non-comment changed lines across all ten files.
Tools/doc_comment_lint.py clean.

(This also supersedes my review note on #925, which suggested renumbering these to #347 → #351 → #277.
That would have destroyed a contributor's provenance — the numbers were pre-fork, not stale.)

Two comment inaccuracies, no behaviour.

The sleep files carried #600 and #690 from the project's pre-fork repo. Neither
resolves here, and worse, both collide: this repo's #600 is an iOS Target Strain
notification and its #690 is the body-location probe, which BodyLocationProbe
cites correctly. So the same number meant two things depending on the file.

Rewritten to references that resolve in THIS repo:
  - the V2 recipe keeps its credit as @sunny-noop, matching how the same
    contributor is credited in HealthExportPlan and SpotHrvReading, and drops the
    dead repo path
  - the V2-flag sites now cite 7.0.0, the release that introduced SleepStagerV2
    here (CHANGELOG.md:240; the file arrived in commit 4da3cfb), plus #277/#351
    for the default-ON claim, which those files already cite a line above
  - HrBroadcaster's credit keeps ryanbr, loses the dead path

github.com/NoopApp/noop 404s and this repo is a fork whose parent no longer
resolves, so every one of those links was dead. Nothing live pointed there:
UpdateChecker and UpdateCheck both read api.github.com/repos/ryanbr/noop, and
both About links go to github.com/ryanbr/noop.

The two AppChangelog entries that mention NoopApp are left alone deliberately —
they are the shipped release notes for the version that made that change, and
rewriting them would falsify the record rather than correct it.

Also: ReportReviewGate described the Oura Tier-B sidecars as capped at 20 MB.
Both dumps enforce 25 MB (OuraActivityDump.maxBytes / OuraMotionDump.maxBytes).
@ryanbr
ryanbr force-pushed the fix/qualify-upstream-refs-and-cap branch from b758a9a to d374b08 Compare July 29, 2026 00:35
@ryanbr ryanbr changed the title Say which tracker an issue number belongs to, and fix the sidecar cap Point issue references at this repo, not a repo that no longer exists Jul 29, 2026
@ryanbr
ryanbr merged commit 53682b4 into main Jul 29, 2026
11 checks passed
@ryanbr
ryanbr deleted the fix/qualify-upstream-refs-and-cap branch August 2, 2026 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant