feat(ops): capture top referrers per repo in weekly snapshot#538
Merged
feat(ops): capture top referrers per repo in weekly snapshot#538
Conversation
Add a third CSV (.outreach/adoption-snapshots-referrers.csv, long format) recording top-10 referrers per repo per snapshot. Today's seed shows the why: across 16 repos in 14 days, only ~8 unique humans arrived from any external content (HN: 2, LinkedIn: 1, Reddit: 1, runcycles.io: 4). This is the single best signal for "is HN/blog/social actually working" because clones are dominated by automation. Weekly trend lets us attribute spikes to specific posts/threads instead of guessing.
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
.outreach/adoption-snapshots-referrers.csv(long format: date, repo, rank, referrer, views, uniques) seeded with today's data across all 16 public repos..github/workflows/adoption-snapshot.ymlto fetchtraffic/popular/referrersper repo and append rows alongside the existing totals + by-repo writes.git addlist.Why
Pulling referrer data today made the picture much sharper than clone counts alone could. In a 14-day window across 16 repos:
github.com(internal navigation, scrapers, indexers)runcycles.io— 4 unique humansTranslation: ~8 unique humans arrived from any external content. Clone counts are dominated by automation. Referrer data is the cleanest signal for whether distribution efforts (HN, LinkedIn, podcasts, blog) are actually moving the needle. Weekly trend lets us attribute traffic spikes to specific posts.
Test plan
gh workflow run adoption-snapshot.ymland verify a PR is opened with rows appended to all three CSVs