Ripgrep AI Policy

#1

Post by singiamtel » Wed, May 27, 2026, 11:40 AM UTC

Re: Ripgrep AI Policy

#2

Post by deng » Wed, May 27, 2026, 9:43 PM UTC

Looking at all the unmerged pull requests in ripgrep, you can see what's going on. I will not link him here, but for instance, there's a "Senior Software Engineer at Microsoft", whose agent created 260 PRs in 211 repos with trivial typo fixes in code comments(!). Almost all of them are rejected (including those in ripgrep), but of course, a few get merged and he now boasts he "contributed" to sqlalchemy, Nim and others... What a time to be alive.

Re: Ripgrep AI Policy

#3

Post by ciupicri » Wed, May 27, 2026, 10:59 PM UTC

> This policy was adapted from uv's AI policy.

Wasn't uv bought by an AI company?

Re: Ripgrep AI Policy

#4

Post by Reubend » Thu, May 28, 2026, 12:27 AM UTC

This is such a refreshing policy. AI code is welcome as long as it's good, but comments have to be human.

If someone can't take the time to write their own replies (in their own words), then it feels fair to assume that they didn't take the time to test, review, and clean whatever code they submitted.

Re: Ripgrep AI Policy

#5

Post by neuronexmachina » Thu, May 28, 2026, 1:12 AM UTC

ciupicri wrote: post #3

> This policy was adapted from uv's AI policy. Wasn't uv bought by an AI company?

Was curious and astral put up their AI policy a couple weeks before the acquisition. Of course, it's quite possible they already knew it was happening: https://github.com/astral-sh/.github/pull/1

That said, I'm kind of surprised ripgrep hasn't been acquired by anyone, considering all the major AI agents use it pretty heavily.

Re: Ripgrep AI Policy

#6

Post by JSR_FDED » Thu, May 28, 2026, 1:38 AM UTC

This is a very elegant way of dealing with slop, whilst still reaping the benefits of smart people using AI to do useful things.

Re: Ripgrep AI Policy

#7

Post by spprashant » Thu, May 28, 2026, 1:54 AM UTC

Sounds about as sane as you could possibly be given the climate.

Re: Ripgrep AI Policy

#8

Post by nextaccountic » Thu, May 28, 2026, 2:44 AM UTC

ciupicri wrote: post #3

> This policy was adapted from uv's AI policy. Wasn't uv bought by an AI company?

burntsushi also works in this company (or worked?). he is actually a developer of uv (or was a couple years ago?)

https://github.com/astral-sh/uv/graphs/contributors?from=9%2...

Re: Ripgrep AI Policy

#9

Post by nextaccountic » Thu, May 28, 2026, 2:46 AM UTC

neuronexmachina wrote: post #5

ciupicri wrote: post #3

> This policy was adapted from uv's AI policy. Wasn't uv bought by an AI company?

Was curious and astral put up their AI policy a couple weeks before the acquisition. Of course, it's quite possible they already knew it was happening: https://github.com/astral-sh/.github/pull/1 That said, I'm kind of surprised ripgrep hasn't been acquired by anyone, considering all the major AI agents use it pretty heavily.

well, ripgrep is not a company.. what means to "buy" an open source project?

companies either "fund" open source developers (usually a pittance), "contribute" code, or if all fails "fork" them, but straight buying, that's something I never see

Re: Ripgrep AI Policy

#10

Post by ramon156 » Thu, May 28, 2026, 6:12 AM UTC

deng wrote: post #2

Looking at all the unmerged pull requests in ripgrep, you can see what's going on. I will not link him here, but for instance, there's a "Senior Software Engineer at Microsoft", whose agent created 260 PRs in 211 repos with trivial typo fixes in code comments(!). Almost all of them are rejected (including those in ripgrep), but of course, a few get merged and he now boasts he "contributed" to sqlalchemy, Nim and othe…

Drive-by PRs have been an issue before, but with AI it's just getting disrespectful