---
title: "Discussion on \"The 20,000-line PR that was actually 47 lines: building ClearPR\" | Hashnode"
description: "Discussion on \"The 20,000-line PR that was actually 47 lines: building ClearPR\". The 20,000-line PR that was actually 47 lines: building ClearPR\n\nSome time back, a teammate opened a PR. The diff said 20,847 lines changed. I clicked, my MacBook fan kicked in, and GitHub started painting the page in those familiar green and red blo..."
url: "https://hashnode.com/posts/the-20000-line-pr-that-was-actually-47-lines-building-clearpr/69f46a4f7d4d8abc9d81cb15"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The 20,000-line PR that was actually 47 lines: building ClearPR](https://vineethnk.hashnode.dev/the-20000-line-pr-that-was-actually-47-lines-building-clearpr?utm_source=hashnode&utm_medium=feed)

The 20,000-line PR that was actually 47 lines: building ClearPR Some time back, a teammate opened a PR. The diff said 20,847 lines changed. I clicked, my MacBook fan kicked in, and GitHub started painting the page in those familiar green and red blo...

May 1 · 10 min read · vineethnk.hashnode.dev  
Read the article

-   [#ai-review](https://hashnode.com/tag/ai-review)
-   [#github-app](https://hashnode.com/tag/github-app)
-   [#nestjs](https://hashnode.com/tag/nestjs)
-   [#tree-sitter](https://hashnode.com/tag/tree-sitter)
-   [#typescript](https://hashnode.com/tag/typescript)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
