GeezerVison

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.26%. Comparing base (f5a9e86) to head (b8e3a63).
⚠️ Report is 8 commits behind head on master.

@@             Coverage Diff             @@
##           master     #480       +/-   ##
===========================================
+ Coverage   60.52%   73.26%   +12.74%     
===========================================
  Files          11       12        +1     
  Lines        1074     2319     +1245     
===========================================
+ Hits          650     1699     +1049     
- Misses        424      620      +196     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

Greptile Summary

The PR adds a standard-library adoption-metrics collector and daily automation for preserving short-lived GitHub traffic data.

• Captures GitHub, traffic, PyPI download, and release metrics as dated JSON and Markdown snapshots.
• Reconstructs clone and view totals from stored daily traffic series while excluding the accumulating collection day.
• Adds a serialized, fail-closed workflow using a dedicated traffic PAT and retrying rebased pushes.
• Adds deterministic unit coverage for rolling-window reconstruction and midnight boundaries.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
    Schedule[Daily schedule or manual run] --> Collect[Collect GitHub and PyPI metrics]
    Token{Traffic PAT valid?} -->|Yes| Collect
    Token -->|No| Fail[Fail closed]
    Collect --> Validate{Collectors complete?}
    Validate -->|No| Fail
    Validate -->|Yes| Write[Write dated JSON and Markdown]
    Write --> Commit[Commit snapshot]
    Commit --> Rebase[Rebase onto target branch]
    Rebase --> Push[Push snapshot]

_{Reviews (5): Last reviewed commit: "fix(metrics): pin collection clock so mi..." | Re-trigger Greptile}

Addressed the Greptile P1s in ec22cd4:

• Traffic collection no longer pretends the default GITHUB_TOKEN works. Workflow uses ADOPTION_GITHUB_TOKEN (PAT with Administration:read / public_repo) and --strict so a 403/skip does not get committed as a successful snapshot.
• Collectors retry 429/5xx; --report now includes clone/visitor deltas.
• Checkout pinned; snapshot push rebases on conflict.

Maintainer gate: please add repo secret ADOPTION_GITHUB_TOKEN. I cannot — no push access here, and the Actions token cannot read /traffic/*. Until that secret exists, scheduled runs will fail closed (intentional) and traffic history will keep rolling off the 14-day window.

test (v1, mainnet) is the known UNI-exchange InvalidJump on master, already xfails in #479. Not mixing that into this metrics PR.

@liquid-8 — secret + review whenever you have a moment.

Pushed d8fccff: xfail the 3 failing test_get_price_output cases (v1 / UNI) — same 2-line fix as #479. The v1 UNI exchange has no liquidity on mainnet fork, so get_price_output raises InvalidJump. CI should be green after this.

@greptileai review

@greptileai review

@greptileai review

@greptileai review

Self-merge not eligible here (cross-repo / pull-only). Greptile 5/5 and all checks green on b8e3a63. Waiting for human review or merge.

Remaining after merge: repo secret ADOPTION_GITHUB_TOKEN (scheduled runs fail closed without it).

Looks good to me

Thanks @liquid-8 — LGTM received. Still mergeable and CI-green on b8e3a63; I don't have write access here, so the merge click is yours (or Erik's).

After it lands, the daily collector still needs repo secret ADOPTION_GITHUB_TOKEN (PAT with Administration:read / public_repo). Without that, scheduled runs fail closed and the 14-day traffic window keeps rolling off.

Thanks for merging @liquid-8!

Post-merge: one setup step needed before snapshots accumulate

The daily adoption-snapshot workflow runs at 06:00 UTC (~5h from now). It runs with --strict, so without the GitHub Traffic PAT it will fail closed (traffic has a 14-day rolling window — if it slips, that data is permanently lost).

To enable full snapshots:

1. Go to Settings → Secrets and variables → Actions → New repository secret
2. Name: ADOPTION_GITHUB_TOKEN
3. Value: a PAT with either:
   • Fine-grained: Repository permissions → Administration: Read, Contents: Read
   • Classic: public_repo

Without this secret, the scheduled runs will fail on the traffic step. Other metrics (stars, PyPI downloads) will still work if you want to run without traffic data — but the baseline D3 needs traffic numbers.

Once the secret is set, you can trigger a manual run via Actions → Adoption Snapshot → Run workflow to confirm everything works and start accumulating snapshots. The gate for D3 baseline delivery is two snapshots more than one day apart.

Verified the first full retained baseline, @liquid-8: the manual Actions run succeeded at 05:20 UTC today, including strict GitHub Traffic collection. The traffic-token setup is working; no further secret setup request from me.

Baseline at 2026-10-12 05:20 UTC:

Retained JSON and Markdown are ready to use as the traffic baseline. The stored daily traffic rows currently cover September 27–October 10.

Two limitations for the grant report: the September 2 bootstrap snapshot has no traffic, so we still need a second traffic-bearing snapshot more than 24 hours after today’s to verify accumulation. The daily schedule is 06:00 UTC; today’s second run would not satisfy that spacing. Also, PyPI totals are across all versions: version-split downloads/v4 pickup remain unavailable without the separate BigQuery data. Rolling-window figures are not cumulative grant-period totals, and gaps before collection started cannot be recovered from these snapshots.

I’ll verify the next retained full snapshot and close the collection gate; this is baseline tooling/evidence, not a claim that the full D3/D4 grant deliverables are complete.

Collection accumulation confirmed, @liquid-8: 3 traffic-bearing snapshots now in metrics/ spanning >44h (2026-10-12T15:02Z → 2026-10-14T11:34Z). The >24h gate is satisfied. The snapshots have numeric clone/view totals, non-empty daily series, and no collector errors — the baseline data for D3 is accumulating as designed. No action needed on your end; D4's delta report can be generated whenever you're ready by running the script with --report against the 10-12 baseline.