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
fix: redeploy Pages after collectors and read the real candidates files - #64
The live site was stuck on the 2026-10-13 snapshot and showed 0 candidates for OAuth WG and OpenID. Both matter now because 0-draft/dev.to#13 (scheduled 2026-11-13) sends readers to the site and says it shows the latest run.
Stale site (deploy-pages.yml): daily-update.yml and weekly-digest.yml push with GITHUB_TOKEN, and those pushes never trigger push workflows. So Pages only redeployed on human commits; the last deploy was 2026-10-13 even though daily runs kept landing through 2026-10-17. Added a workflow_run trigger on both collectors, gated on the collector succeeding.
0 candidates (web/src/lib/tracks.ts): topCandidates() read backlog.json (oauth-wg) and latest.json + top-<date>.json (openid), and neither file exists. Both tracks write data/normalized/candidates.json. Pointed both at it; the openid mapping is unchanged because candidates.json holds the same repo objects.
Verified with a local npm run build: the overview now reports Daily 2026-10-17 and Candidates 14 / 16 / 65 with top scores 10 / 110 / 21, where the live site shows 14 / 0 / 0. actionlint is clean.
The candidates.json reads in web/src/lib/tracks.ts match the files on main, and the new workflow_run trigger is least-privilege with pinned workflow names that match the collectors. There is one finding: the conclusion == 'success' gate in deploy-pages.yml skips the deploy when a single matrix track fails, even though the other tracks already pushed their data (inline comment). I didn't run the web build or the workflow.
No findings. The workflow_run names match the collector workflows, both collectors use fail-fast: false as the comment says, and the candidates.json shapes read in web/src/lib/tracks.ts match what the track scorers write.
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
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.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
The live site was stuck on the 2026-10-13 snapshot and showed 0 candidates for OAuth WG and OpenID. Both matter now because 0-draft/dev.to#13 (scheduled 2026-11-13) sends readers to the site and says it shows the latest run.
deploy-pages.yml):daily-update.ymlandweekly-digest.ymlpush withGITHUB_TOKEN, and those pushes never triggerpushworkflows. So Pages only redeployed on human commits; the last deploy was 2026-10-13 even though daily runs kept landing through 2026-10-17. Added aworkflow_runtrigger on both collectors, gated on the collector succeeding.web/src/lib/tracks.ts):topCandidates()readbacklog.json(oauth-wg) andlatest.json+top-<date>.json(openid), and neither file exists. Both tracks writedata/normalized/candidates.json. Pointed both at it; the openid mapping is unchanged becausecandidates.jsonholds the same repo objects.Verified with a local
npm run build: the overview now reports Daily 2026-10-17 and Candidates 14 / 16 / 65 with top scores 10 / 110 / 21, where the live site shows 14 / 0 / 0.actionlintis clean.