The Developer Advocate role has one objective, developer awareness, and Trunk's whole pitch is that flaky tests waste CI time. GitHub exposes every public workflow run with its attempt count, so the re-run rate of any open-source project can be measured from outside, including projects run by Trunk's own logo customers such as Supabase and PostHog.
First action
Write the script that reads workflow runs for one repository and computes its re-run rate.
How to measure it
Free Flaky Tests installs from the report
- Now
- –
- Target
- 25 projects
- By
- 6 weeks
Steps
Write the collector
GitHub Actions runs and attempts for 90 days.
Senior Developer Advocate 2 days
Pick the 100 repos
Most active by pull requests, across languages.
Senior Developer Advocate 2 hours
Compute the numbers
Re-run rate, CI minutes lost, worst workflows.
Senior Developer Advocate 1 day
Write the method
What counts as a re-run, and the limits.
CTO 2 hours
Publish the report
Ranked table, charts, method and a free-install offer.
Senior Developer Advocate 2 days
Tell maintainers
A friendly note to each top-20 project with their number.
Senior Developer Advocate 1 day
Hand leads to Sales
Company-backed projects go to Sales with the data.
Sales team ongoing
Why it works
Pull 90 days of GitHub Actions runs for the 100 most active public repositories, compute the share of runs that needed a re-run and the CI minutes lost, publish a ranked report with the method, and offer each maintainer a free Flaky Tests setup.
It is original data no competitor has, it names projects developers care about (which gets shared), and every listed project is a lead: maintainers and the companies behind them see their own number.
Risks and how to handle them
Projects dislike being ranked
Lead with the method, offer help, and let maintainers add context.
Re-runs have other causes
Say so in the method and show it as an estimate.
Evidence
- Search resultsGitHub's REST API exposes workflow runs with a run_attempt count for public repositories, so re-run rates can be measured from outside.Source
- HiringSenior Developer Advocate: speak at developer and platform engineering conferences (about 30% travel) and own the event strategy with Sales on lead capture; own blog posts, webinars, demo videos and case studies; "Show up where platform engineers talk shop"; "Docs are a conversion lever - you're accountable for their quality"; one objective, "drive developer awareness", with top-of-funnel metrics that convert to pipeline.Source
- Your websiteHomepage: "Keep CI Green: Eliminate flaky tests and merge bottlenecks"; Flaky Tests (automatic quarantine, PR summaries, Linear and Jira tickets, AI failure analysis) and a Merge Queue sold as an upgrade to GitHub's (anti-flake protection, batches of up to 100 PRs, parallel queues); logos include Brex, Zillow, Exa, Supabase, PostHog, Faire, Ramp, Cockroach Labs, Retool and Google X; the main call to action is "Book a demo".Source
- Your websiteCustomer stories: Brex (P90 time to merge down 30%, half of merge-queue failures eliminated), Faire (330 hours saved in 35 days), BetterUp (CI reliability from 70% to 90%+), Caseware (75% merge-time reduction on day one), TheyDo (94% of failing CI jobs now go green), Glydways (160 PRs a week). Only the Descript story quotes a named person: "Agent-based PRs is more of a thing now. And also non-engineers opening PRs is a thing now."Source