AI is approving our pull requests
Engineering Published Apr 21, 2026 AI is approving our pull requests: Here’s how we made it safe We’re producing more code than ever at Intercom. Here’s how we’re safely using AI for PR approval. Kesha Mykhailov Niamh Young 9 min At Intercom, shipping is our heartbeat.
- ▪Engineering Published Apr 21, 2026 AI is approving our pull requests: Here’s how we made it safe We’re producing more code than ever at Intercom.
- ▪Here’s how we’re safely using AI for PR approval.
- ▪Kesha Mykhailov Niamh Young 9 min At Intercom, shipping is our heartbeat.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,379 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Intercom Blog |
| Canonical URL | https://www.intercom.com/blog/ai-is-approving-our-pull-requests-heres-how-we-made-it-safe/ |
| Publication time | Tue, 11 Aug 2026 06:30:27 +0000 |
| Retrieval time | 2026-08-11T06:35:43.134Z |
| Last seen | 2026-08-11T06:35:43.134Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | gHtX4Fz4LIKM · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Engineering Published Apr 21, 2026 AI is approving our pull requests: Here’s how we made it safe We’re producing more code than ever at Intercom. Here’s how we’re safely using AI for PR approval. Kesha Mykhailov Niamh Young 9 min At Intercom, shipping is our heartbeat. We push code to production hundreds of times a day. Engineers, engineering managers, designers, and PMs all contribute to this, safely. The average time from merging code to it running in production is 12 minutes. We’ve long held a belief that might sound counterintuitive: speed is not the enemy of safety. It’s a prerequisite for it. Accumulating code creates risk. Shipping small batches minimizes it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Intercom Blog.
Discussion
0 commentsMore from The Intercom Blog
