Repository navigation
Read the latest view counts from the staged stats - #584
Merged
Alejandro Lopez (soyalejolopez) merged 2 commits intoNov 2, 2026
Merged
Conversation
The daily workflow keeps a fresh resource-stats.json on automation/traffic-stats-staging, but publishing it to master takes a weekly pull request that Actions cannot open under the org's policy, so the site's counts were only as fresh as the last merged weekly PR. The catalog and the resource pages now also read the staged file from raw.githubusercontent.com (assets/live-stats.js) and take only its view counts. The committed file stays the source for everything else and the fallback whenever the staged file cannot be read in 1.5 seconds, is older than the committed file, or was counted by a different method (sources.views). No token or PR is needed. - The privacy notice discloses the request (no cookies, no referrer). - Tests cover accept/reject rules, fetch failures, the URL matching the workflow's staging branch, and the wiring in the catalog and the resource pages. - traffic-data/README.md documents the behavior and what to change if the branch is renamed. - Regenerated the 58 resource pages for the new script tag. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
🛰️ PR Sweeper reportRisk: 🟢 LOW · Security gate: ✅ passing · Files: 65 🔒 Automated guardrails (authoritative)
🤖 Dual-model AI review (advisory)AI review unavailable for this run (models not reachable or no diff). Guardrails above are unaffected.
The automated guardrails are authoritative and gate the security status. The AI review is advisory and never auto-merges. Thanks for contributing to FastTrack! 🛩️ |
CodeQL flags substring tests on URLs (js/incomplete-url-substring-sanitization). These are test assertions, not sanitization, but a substring test on a URL also proves little about the host it names. Compare against the exact set of hrefs on each page, and check the privacy notice against the set of hostnames it names, using the host of the live stats URL instead of a hard-coded string. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Alejandro Lopez (soyalejolopez)
deleted the
read-live-stats-from-staging
branch
November 2, 2026 20:01
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
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.
The daily workflow keeps a fresh resource-stats.json on automation/traffic-stats-staging, but publishing it to master takes a weekly pull request that Actions cannot open under the org's policy, so the site's counts were only as fresh as the last merged weekly PR.
The catalog and the resource pages now also read the staged file from raw.githubusercontent.com (assets/live-stats.js) and take only its view counts. The committed file stays the source for everything else and the fallback whenever the staged file cannot be read in 1.5 seconds, is older than the committed file, or was counted by a different method (sources.views). No token or PR is needed.