# Pull Requests Are for Humans > [!question] Lingering Questions > - Where exactly is the line between acceptable AI-assisted authoring (human curates the draft) and the "unfiltered pipeline" McCue condemns? > - Does the "rude" framing scale to paid internal teams, or is the ethical weight specific to volunteer reviewer labor? > [!idea] Article Ideas > - "AI-assisted contribution etiquette" talk/post for WordPress and OSS audiences, using McCue's escalation ladder (description → pipeline → back-and-forth → OSS rudeness). > - A PR-template field prompting "why this approach, broader context, user impact" to nudge human context into descriptions. > [!link] Cross Reference > - Connects to reliability/trust-as-moat thinking ([[Why Reliability Is the Ultimate Product Moat]]) — both treat unglamorous human process as the real differentiator AI can't replace. > - Open-source volunteer-labor burden theme recurs across this batch (theme directory abandonment, CHAOSS podcast sunset) — reviewer time as a scarce resource worth protecting. > [!abstract] Vocabulary > - **Unfiltered pipeline** — a PR that goes straight from AI prompt to submission with no human involvement, pure burden on the reviewer. > - **False certainty** — McCue's term for what happens when review comments (often probes/invitations to discuss) get piped into an agent that treats every comment as a directive. ## Metadata - Source: [[3. Resources/Readwise/Articles/Pull Requests Are for Humans]] - Author: Ryan McCue (WordPress REST API lead, Human Made) - URL: https://journal.rmccue.io/498/pull-requests-are-for-humans/ - Category: Article ## Author's Thesis **What is the author saying?** Pull requests are a human-to-human communication medium; AI-written code is fine, but AI-written descriptions, reviews, and back-and-forth hollow out what review is actually for. **What of it?** Code review's less obvious value is team knowledge transfer, not just a quality gate — automating both ends of that exchange removes a benefit AI can't replace, and in open source it shifts real cost onto unpaid volunteer reviewers. ## Key Arguments 1. Reviews are a primary channel for building and sharing engineering knowledge across a team — quality is the visible goal, learning is the deeper one. 2. Feeding review comments into an agent introduces "false certainty": comments are often discussion probes, not directives, and an agent flattens that nuance. 3. Making a volunteer reviewer handle an AI's back-and-forth escalates the critique from inefficiency to an ethical claim — it's "outright rude." ## Claim Atoms ### Code review is a primary knowledge-sharing channel > [!quote] ID:rw_h1 > it is one of the primary ways we build and share our engineering knowledge across the team **Context & use**: The essay's strongest, least-obvious claim — review value isn't only quality, it's team learning, so automating the human side removes something AI can't replace. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### Feeding review comments to an agent fabricates false certainty > [!quote] ID:rw_h2 > Feeding those comments directly into an agent introduces a false certainty that isn't intended in the feedback. **Context & use**: Review comments are often probes; an agent reads every one as a directive, forcing over-correction. **Tags**: #xref #articleseed <!-- atomicity: 1 idea ✓ --> ### Making volunteers handle your AI back-and-forth is rude > [!quote] ID:rw_h3 > using AI to create pull requests and handle this back and forth goes beyond degrading this process – it's outright rude. **Context & use**: Closing paragraph, OSS-specific. Reframes the critique from efficiency to ethics — volunteer reviewer time is unpaid labor. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ## Permanent Candidates - [[Automating Both Ends Of A Review Collapses Its Value]] — a code review only creates knowledge when at least one human is genuinely present on each side. ## Processing Checklist - [x] Verbatim quotes captured with source location - [x] Atomicity markers on all atoms - [x] Permanent candidate identified and drafted - [x] Konik triage callouts populated - [x] Tags limited to Konik-7 pool - [x] MOC links proposed (not written) ## Links - [[3. Resources/MOCs/DevRel MOC]] — contributor etiquette and PR-review norms as a DevRel/education surface. - [[3. Resources/MOCs/Open Source Governance MOC]] — volunteer reviewer labor and AI-use policy as a governance question.