How 
Astro ships
Astro released every week of the last 12; pull requests got a first review in 8.1 hours and merged in 21 hours (median).
- Repository
- withastro/astro
- Updated
- Oct 18
Release weeks
0/12
PRs merged
31/week
Commits
43/week
Merged PRs per week
Reviewed < 1 dayWaited longerNo review
42
Jul 26Aug 9Aug 23Sep 6Sep 20Oct 4
Reviews
Last 12 weeks- Review wait
0.0h
- Time to merge
0h
- Merged unreviewed
0%
Commits
1,182 commitsLessMore
People
PRsReviewsCommitsmatthewp64248126
astrobot-houston67–53
ematipico2715041
florian-lefebvre1711144
Princesseuh244734
How code gets to production
Experimental · read Oct 18 from branch rules and PR checks
Gates on main
Rules every merge must pass, as set today
- Changes go through a PR
- Not public
- Approvals required
- Not public
- Code owners must approve
- Not public
- Required checks
- None
- Force-push blocked
- Signed commits
- Linear history
- Merge queue
Of the last 50 merges: 50 approved.
What runs on every PR
Checks that ran on the last 50 merged PRs
100%
had any check
5
merged failing
- BuildCheck mergeability, CI, Examples astro check100%
- SecurityGitHub Actions Security Analysis with zizmor 🌈, GitHub Advanced Security, Semgrep OSS scan100%
- Previewpkg.pr.new14%
- PerformanceCodSpeed, Continuous benchmark26%
- Dependenciesrenovate56%
- OtherDiff Dependencies, GitHub Actions98%
- HousekeepingCleanup cache, Label PRs100%
How other teams ship
Same numbers, same 12 weeks, from their public GitHub.
Payload
payloadcms/payload
- Review wait
- 2h
- To merge
- 12h
- Shipped
- 8/12
Angular
angular/angular
- Review wait
- 2.8h
- To merge
- 24h
- Shipped
- 12/12
Electron
electron/electron
- Review wait
- 3.2h
- To merge
- 9.1h
- Shipped
- 12/12
Tauri
tauri-apps/tauri
- Review wait
- 9.7h
- To merge
- 34h
- Shipped
- 10/12
NestJS
nestjs/nest
- Review wait
- 4.5h
- To merge
- 13h
- Shipped
- 6/12
Expo
expo/expo
- Review wait
- 1.1h
- To merge
- 8.4h
- Shipped
- 4/12
How we count
- Weeks with a release
- Weeks in the last 12 with at least one GitHub release, production deploy, merge to a production branch or version tag, whichever the team uses most.
- Review wait
- Median time from a pull request being ready for review to its first review by someone else.
- Time to merge
- Median time from opening a pull request to merging it. Automerges with no review are left out.
- Merged without review
- Share of merged pull requests that nobody other than the author reviewed.
- People and agents
- Everyone who committed, merged or reviewed in the last 12 weeks. AI agents that work under their own account are listed apart.
- By AI agents
- Share of merged pull requests opened by an AI agent, or of commits made by one, whichever is higher. Agents are Claude, Copilot, Codex, Devin and similar, plus a team's own bots whose pull requests read like an engineer's (varied titles, a written description), such as opencode-agent or posthog[bot]. Release, dependency and CI bots don't count.
- Reviewed by AI
- Share of merged pull requests that an AI reviewer commented on: CodeRabbit, Copilot, Greptile, Codex or a team's own review bot. Any bot that leaves review comments counts; approval-only, CI and code-scanning bots don't. AI reviews don't count toward review wait or merged without review.