GoogleCloudPlatform/k8s-config-connector velocity

Velocity & Acceleration Rate. The rolling velocity and acceleration of PR merges. Positive acceleration (green bars) reflects increasing speed, with the largest positive shifts occurring as the AI agent ramps up operations.

Year-over-year. 2026 bars (green) overlap each prior month against 2025 (blue) and 2024 (grey). Look for months where the green bar clears the blue — that's where the repo is ahead of its prior-year self.

Cumulative curve. The dashed grey line is a constant-rate reference between window start and today. The total curve bowing above the line means throughput has been faster recently than the window average; the AI-agent line (green) is the slice that bent the average.

Cycle Time (Merge Lead Time). Median duration (days) from PR creation to merge, by author class. Gaps between the human line (blue) and the AI line (green) show the speed multiplier of automation.

AI-agent share. Green bars = AI-agent merges per month. Dark-green line = AI share of all merges that month. The inflection in late 2025 / early 2026 is when codebot-robot went from occasional commits to ~30+ merges/month.

Active humans. Number of distinct human logins that merged at least one PR in the month. Tells you whether the team is growing — or whether one or two heavy committers are carrying the load.

Default-branch commits. One commit per squash-merge plus any direct pushes, classified by GitHub login. A cleaner picture of repo throughput than PR counts when the project uses squash merges.

data: prs.json (4,598 PRs) · commits.json · classification: codebot-robot + google-labs-jules[bot] counted as AI agents; dependabot/renovate as dep-bots; everything else as human (incl. unknown Bot-typed accounts — revisit if a new automation appears at the top of the contributors list).