Pull request

Evidence (19)

• 6The New Stack·8/12/2026product_launch
  CodeRabbit launches Agentic Change Management for AI-driven software change

  CodeRabbit announced an Agentic Change Management control layer to help teams govern software changes created by both human developers and AI agents. The company argues that issue tracking is becoming less central as pull requests turn into the main auditable decision point for planning, review, and shipping code.

• 7The New Stack·8/9/2026research
  AI speeds up coding, but engineering output stays flat

  DX’s State of AI Impact in Engineering report says AI tooling has made individual developers faster, but organizational velocity has not improved in step. The report points to growing coordination overhead, flat innovation ratios, and weaker change confidence, especially in larger companies and larger pull requests.

• 4The New Stack·8/8/2026research
  AI Adoption vs. AI Usage in Engineering Teams

  The article argues that common AI adoption metrics, such as seat activations, token spend, and weekly active usage, mostly measure usage rather than real workflow change. It says lasting adoption only happens when AI becomes part of team norms or recurring processes, not just individual experimentation.

• 6InfoQ·8/7/2026product_launch
  Spotify Details AI Agent for Fleet-Wide Codebase Migrations

  Spotify engineers Jo Kelly-Fenton and Aleksandar Mitic describe Honk, an AI coding agent built to manage large-scale codebase migrations across thousands of repositories. The talk focuses on separating CI verification runtime from the agent, handling pull request bottlenecks, and enforcing standardization across the engineering fleet.

• 4InfoQ·8/7/2026framework_update
  Rootly Ends Small PR Rule as AI Agent Code Generation Grows

  Rootly says its long-standing rule favoring small pull requests is no longer effective because AI agents now generate most of its code. The company is shifting review criteria toward blast radius, using feature flags and rollback readiness to judge risk instead of line count.

• 6Hacker News·8/5/2026open_source
  Rust Project Adopts Public Policy for LLM Use in rust-lang/rust

  Several teams in the Rust project have adopted a new policy governing how large language models may be used in contributions to the rust-lang/rust monorepo. The policy is intended to clarify expectations for contributors and reviewers, especially around LLM-generated code, issue reporting, and quoted LLM output.

• 6The New Stack·7/23/2026research
  How regulated organizations can safely speed up AI coding

  The article argues that regulated organizations can use AI to increase software delivery speed, but only if verification becomes a continuous part of the engineering process. It highlights how AI-assisted development and agentic workflows can help domain experts and engineers collaborate more effectively while maintaining accountability, security, and compliance.

• 5The New Stack·7/19/2026research
  AI Is Pushing Code Review Upstream

  The article argues that traditional pull-request-based code review is becoming a poor fit for AI-assisted software development, where large amounts of code are generated quickly. It suggests teams should review intent, specs, and acceptance criteria earlier in the workflow rather than waiting until merge time.

• 4The New Stack·7/16/2026research
  AI Hasn't Moved the Software Bottleneck to Code Review

  The article argues that AI coding tools have not shifted the main bottleneck from coding to code review. Instead, it says the real constraint is usually downstream in testing, deployment, and release batching, where changes pile up before reaching users.

• 6The New Stack·7/11/2026research
  AI code reviews expose a new software bottleneck

  The article argues that merge quality should be treated as an explicit contract, especially as coding agents increase pull request volume. It says traditional pipelines usually verify only the first three layers of confidence, while real system behavior testing remains the costly missing layer that often catches microservice bugs.

• 3Simon Willison·7/8/2026framework_update
  Kenton Varda pauses AI-written change descriptions

  Kenton Varda said he has imposed a moratorium on AI-written change descriptions, including pull request messages, commit messages, and issues or tickets. He said these descriptions were often too focused on low-level code details and missed the broader context needed for review.

• 7GitHub Blog·7/7/2026open_source
  GitHub reports faster global open source collaboration in Q1 2026

  GitHub says outbound open source collaboration rose 16% quarter over quarter in Q1 2026, the second-highest quarterly growth rate in its data since 2020. The update also highlights economy-level trends and new maintainer tools, including pull request limits, repo-level contribution controls, pinned comments, temporary interaction limits, and performance improvements for pull requests and issue navigation.

• 6The New Stack·7/7/2026research
  Rethinking code review in the AI coding era

  The article argues that traditional code review is no longer keeping up with AI-assisted development, where code can be produced far faster than humans can review it. It splits review into two separate jobs—alignment and standards-checking—and suggests that intent should be captured during development rather than only in pull requests.

• 4The New Stack·7/6/2026research
  Developers rethink code review as a bug-finding tool

  The article argues that code review is often misused as a bug-finding mechanism, a role that senior engineer Mark Dominus says it is generally not suited for. Dominus and QA engineer Mikhail Golikov say review is more valuable for assessing maintainability, spotting hard-to-understand changes, and revealing when a change set is too large or complex to review effectively.

• 6Hacker News·7/5/2026open_source
  Flipper Zero resumes firmware development with new community rules

  Flipper Devices says it will keep maintaining Flipper Zero firmware after backlash over a perceived halt in development. The company also plans to formalize community participation through GitHub Discussions voting, clearer pull request guidelines, and mandatory integration testing.

• 6GitHub Blog·6/30/2026product_launch
  GitHub adds license compliance checks for dependencies

  GitHub says its Open Source Program Office has moved from internal tools to the new GitHub License Compliance feature to review dependency licenses directly in pull requests. The rollout uses rulesets and an evaluate mode to help teams align dependency reviews with company policy without immediately blocking development.

• 4Hacker News·6/28/2026research
  Reflections on AI’s Changing Software Engineering Workflow

  The article argues that AI has changed software development from writing code and tests directly to prompting, reviewing, and editing AI-generated output. It emphasizes that experienced engineers still need to catch legal, security, performance, and system-level issues that AI may miss.

• 6InfoQ·6/26/2026research
  How AI Is Disrupting the SDLC

  Michael Webster describes how headless AI agents are generating massive pull requests that slow human review and add technical debt to software delivery pipelines. He recommends test impact analysis and automated validation pipelines to verify agent-generated code while maintaining stability.

• 7GitHub Blog·6/18/2026framework_update
  GitHub adds pull request limits to reduce repository noise

  GitHub has introduced configurable pull request limits that cap how many open pull requests a user without write access can have in a repository at once. The feature is meant to reduce low-quality noise, help maintainers manage review volume, and improve how contributions are prioritized; draft pull requests do not count, and trusted contributors can be exempted.