Re: A quick thought on AI-generated bulk PRs

Hi Olivier,

I agree. As of now getting 100-200 Github mails within a single day 
happens more and more, brings at least me to mental exhaustion. Your 
suggestion sounds like a good way to have full covered PR on a single 
repo first and then scale it, where (hopefully) less reviews needs to be 
done.

Matthias


Am 10.08.2026 um 23:28 schrieb Olivier Lamy:
> Hi there,
> Just to be clear upfront: I’m totally pro-AI tools and use them myself.
> But I’ve noticed a pattern lately with bulk changes that I think we
> need to tweak.
> Right now, the workflow looks a bit like this:
> 1. Run a prompt in "yolo" mode to make massive changes across a bunch
> of repos all at once.
> 2. Merge the PRs almost immediately.
> 3. Realise the initial prompt missed something, which triggers another
> massive batch of PRs to fix the first batch.
> 4. back to 1.
>
> The main issue here is notification fatigue. We’re getting blasted
> with so many emails and alerts that it’s impossible to keep up. When
> that happens, we tune out the noise and stop reviewing entirely, which
> is exactly when real issues slip through the cracks.
>
> Since AI is incredibly useful for these kinds of bulk updates, I think
> we can do this more effectively/wizely.
> Could we try this approach instead?
>
> Start small: Run the prompt and generate a PR for just one repo first.
> Review: Have the community conduct a thorough, in-depth review of that
> single AI-generated PR.
> Refine: Tweak the prompt based on the feedback. Once it's solid, we
> can save it as a reusable "skill" that the community trusts.
>
> Scale up: Once the single repo is good to go, then roll the prompt out
> to the rest of the repos.
>
> I think slowing down just a little bit at the start will cut down on
> the noise, save us a lot of context-switching, and make us all way
> more confident in the code we're merging.
>
> Thoughts?
>
> Thanks,
> Olivier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>