---
title: Please Stop Pasting AI Code Into My Pull Requests
description: "Team etiquette for AI-assisted work: what to paste, what to synthesize, and why pasting AI code into a pull request unread makes your review my problem."
canonical: https://lukeocodes.dev/pasting-ai-code
type: article
locale: en_GB
published: 2026-08-20T00:00:00.000Z
modified: 2026-08-20T00:00:00.000Z
authors:
  - Luke Oliff
section: Opinion
tags:
  - Opinion
  - Developer Experience
  - ai
  - code review
  - pull requests
  - etiquette
  - hacker news
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/pasting-ai-code#article
        headline: Please Stop Pasting AI Code Into My Pull Requests
        alternativeHeadline: Please Stop Pasting AI Code Into My Pull Requests
        description: "Team etiquette for AI-assisted work: what to paste, what to synthesize, and why pasting AI code into a pull request unread makes your review my problem."
        datePublished: 2026-08-20T00:00:00.000Z
        dateModified: 2026-08-20T00:00:00.000Z
        url: https://lukeocodes.dev/pasting-ai-code
        mainEntityOfPage: https://lukeocodes.dev/pasting-ai-code
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Opinion, Developer Experience, ai, code review, pull requests, etiquette, hacker news
        articleSection: Opinion
        about:
          - "@type": Organization
            name: Hacker News
          - "@type": SoftwareApplication
            name: ChatGPT
          - "@type": Thing
            name: Developer Experience
        abstract: A pull request is a claim you own. If you paste AI code you haven't read, you're making that claim on a model's behalf, and the model isn't on the on-call rota when the thing breaks.
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=Please+Stop+Pasting+AI+Code+Into+My+Pull+Requests&d=Team+etiquette+for+AI-assisted+work%3A+what+to+paste%2C+what+to+synthesize%2C+and+why+pasting+AI+code+into+a+pull+request+unread+makes+your+review+my+problem.&e=Writing
        wordCount: 569
        timeRequired: PT3M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: Please Stop Pasting AI Code Into My Pull Requests
            item: https://lukeocodes.dev/pasting-ai-code
      - "@type": FAQPage
        "@id": https://lukeocodes.dev/pasting-ai-code#faq
        mainEntity:
          - "@type": Question
            name: Is it fine to use AI to write my pull request?
            acceptedAnswer:
              "@type": Answer
              text: Yes. Use whatever gets you there. The rule isn't don't use the model, it's read what it wrote and be able to defend every line before you ask me to merge it.
          - "@type": Question
            name: What should I do with a long AI explanation before posting it?
            acceptedAnswer:
              "@type": Answer
              text: Cut it to the part that actually answers the question, put it in your own words, and say plainly if the model changed your mind. A short reply from you beats a wall of text from a model.
          - "@type": Question
            name: How is this different from pasting a Stack Overflow answer?
            acceptedAnswer:
              "@type": Answer
              text: It isn't, much. Pasting a Stack Overflow snippet you didn't read was always bad. AI just made it frictionless to do at scale, so the old etiquette now matters far more than it did.
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# Please Stop Pasting AI Code Into My Pull Requests

Aug 2026 · [Opinion](/blog/category/opinion) · 3 min read · [Luke Oliff](/authors/luke)

**TL;DR:** A pull request is a claim you own. If you paste AI code you haven't read, you're making that claim on a model's behalf, and the model isn't on the on-call rota when the thing breaks.

Pasting AI code into a pull request without reading it first is the fastest way to make your review my problem. If you can't explain what a diff does, I can't merge it, and no amount of confident model prose changes that. Paste the reasoning you actually stand behind, not the wall of text a chatbot handed you.

On 20 August 2026 a one-page site called dontpastetheai.com hit the front page of Hacker News with [over a thousand points](https://news.ycombinator.com/item?id=49371857). One request: stop pasting a chatbot's answer at someone who asked you a question. It admits at the bottom that it's half satire, a spiritual cousin of nohello.net. The joke lands because it's true, and the same etiquette applies to code.

## Why pasting AI code unread breaks a team

A pull request is a claim. You're telling me this change is correct, you understand it, and you'll own it when it pages someone at 2am. When you paste code you haven't read, you're making that claim on a model's behalf. The model isn't on the rota. You are.

The trap is that generated code is plausible. It compiles. The tests you asked for pass, because the same model wrote those too. And it can still be wrong in a way that only surfaces under real load, on a Friday, three weeks after everyone forgot the PR existed. My review time is the thing standing between that diff and production, and I'd rather spend it on your judgement than on decoding a model's.

I've reviewed changes where the author clearly couldn't answer "why this and not the obvious alternative?" That's the tell. Not that AI was used. That nobody was home.

## What to paste, and what to synthesize

Paste code you've read line by line and can defend under questioning. That's the whole bar. If a reviewer asks why you reached for a lock there, "the model suggested it" is not an answer, it's a confession.

Synthesize the explanation in your own words. If the model's summary genuinely helped, quote the useful two sentences and say why, the same way you'd cite a colleague. Don't drop 800 words of generated rationale into the description and call it documentation. I will read exactly none of it, and neither will the next person.

Mark the parts you're unsure about. "I let the model draft the retry logic and I'm not confident about the backoff" is worth more than a clean-looking PR that quietly hides the one bit you don't understand. Honesty about the seams is how I know where to actually look.

## What should never ship unread

Some things don't get the benefit of the doubt. Database migrations, because a generated one can drop a column with total confidence. Anything touching auth or money, because plausible-and-wrong is catastrophic there. Regexes and date handling, because those are where models bluff hardest. And any dependency the model added on its own, because a hallucinated or typosquatted package name is a supply-chain incident waiting for a `npm install`.

Read those yourself. Every time. No exceptions for a tight deadline, because the deadline is exactly when the unread migration bites.

None of this is anti-AI. I use it all day. The line is simple: the model is a tool you're accountable for, not a co-author you can blame. Bring me the version you'd defend if the model had never existed. That one I'll merge.

[← Newer: The Rust CLI Tools That Replaced My Coreutils](/rust-cli-replacements)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
