惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The Cloudflare Blog
L
LangChain Blog
WordPress大学
WordPress大学
V
V2EX
M
MIT News - Artificial intelligence
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Stack Overflow Blog
Stack Overflow Blog
J
Java Code Geeks
F
Fortinet All Blogs
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
腾讯CDC
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
D
Docker
Recent Announcements
Recent Announcements
GbyAI
GbyAI
博客园 - 叶小钗
小众软件
小众软件
Hugging Face - Blog
Hugging Face - Blog
T
The Blog of Author Tim Ferriss
人人都是产品经理
人人都是产品经理
Engineering at Meta
Engineering at Meta
Y
Y Combinator Blog
雷峰网
雷峰网
The GitHub Blog
The GitHub Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
When Your Pull Request Has More AI Reviewers Than Humans
neither galax · 2026-06-16 · via DEV Community
Cover image for When Your Pull Request Has More AI Reviewers Than Humans

neither galax

Recently, I submitted a pull request to a project and had an experience that felt very different from the usual OSS workflow in the past.

Instead of the typical back-and-forth with a human maintainer, most of the interaction in my PR came from automated systems: Copilot suggestions, Vercel-related checks, and CI-driven review comments. The maintainer eventually approved the PR with minimal direct discussion, and it was merged successfully.

What stood out to me wasn't just that the PR got merged, but how the review process felt distributed across multiple non-human participants.

A different kind of PR conversation

In this case, I found myself responding to:

  • Copilot-style suggestions embedded in the workflow
  • Automated review comments triggered by code changes
  • Vercel’s deployment feedback loop during preview builds
  • CI checks acting as silent gatekeepers

It wasn’t one reviewer giving feedback—it was a collection of systems continuously reacting to changes. At times, it honestly felt like maintaining a conversation with multiple tools rather than collaborating with a single maintainer.

The maintainer's role felt different

What stood out most was how little direct back-and-forth there was with the maintainer during the process. Instead, it felt more like the automation handled the detailed feedback loop, which is pointing out issues, validating fixes, and checking consistency, while the maintainer stepped in later to look at the overall direction and give the final approval.

So, the human part wasn't really about line-by-line discussion. It was more like a final layer of judgment once everything else had already settled.

At that point, it made me wonder, are we already moving toward a setup where the human role becomes mostly invisible during the process, only stepping in at the end to hit "approve"?

Open questions for the community

I’m curious how you are experiencing this shift:

  • How do you feel about AI-assisted PR reviews on either side (maintainer or contributor)?
  • Have you noticed a change in the depth or tone of discussions in your repositories?
  • Do you think human review is becoming lighter, or just differently focused?
  • Where do you personally draw the line between “useful automation” and “loss of human context”?

It feels like we are entering a phase where PRs (and maybe issues as well) are no longer human-to-human conversations, but hybrid interactions between devs, bots, and CI systems. And I am not fully sure yet whether that's a net positive or just a new normal.