fix: distinguish per-category PR checks and correct D1 database binding#58
Merged
Conversation
- postCheckRun() now names the Check Run "Coverage Tracker (<category>)" for non-default categories instead of always "Coverage Tracker", so backend and frontend PR checks no longer collide under one identical name with no way to tell them apart. - wrangler.json's D1 binding pointed at "coverage" (a stale, empty database) instead of "coverage-demo" (the database actually holding production data). Already corrected live via manual migration + deploy; this commits the config fix so the repo matches production. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
demo-coveragetracker-dev | 502e3e4 | Commit Preview URL Branch Preview URL |
Jul 07 2026, 01:44 AM |
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
1 participant
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
postCheckRun()now names the Check RunCoverage Tracker (<category>)for any non-default category (Coverage Trackerunchanged fordefault). Previously both thebackendandfrontendjobs posted an identically-namedCoverage Trackercheck, so a PR showed two indistinguishable checks — the exact distinction the category feature exists to provide. Rebuiltdist/index.jsto ship the change.wrangler.json's D1 binding pointeddatabase_nameat"coverage"— a stale, empty database — instead of"coverage-demo", which holds the actual production data (9 projects, 23 coverage runs). This caused the live dashboard at demo.coveragetracker.dev to show no data after a deploy. Already fixed live: applied migration0003_categories.sqltocoverage-demo(all rows correctly backfilled tocategory='default', no data lost) and redeployed with the corrected binding. This commit brings the checked-in config in sync with what's now running in production.Test plan
npm test(.github/actions/report) — 105/105 passing, including 2 new tests covering the category-suffixed check namenpm run typecheck(.github/actions/report) — cleancoverage-demohas migration 0003 applied and all 9 projects / 23 runs intact;wrangler deployoutput confirmsenv.DB (coverage-demo); demo.coveragetracker.dev dashboard confirmed showing data again🤖 Generated with Claude Code