A Label Is Not a Review: Following One Closed Merge Request

Description and use

A label for "AI nonsense" replaced a proper review, causing a valid performance fix to be closed and the issue to be addressed months later, increasing effort.

Problem

A quick human check labeled a merge request as AI‑generated, leading to its closure without review, even though the change was a legitimate performance improvement.

Outcome

A quick label replaced a proper review, causing a valid performance fix to be lost and the problem to be addressed later at higher cost.

Workflow

• Contributor opens merge request to speed up a page
• Maintainer marks it as draft and labels it "AI nonsense"
• Contributor closes the merge request
• No review or discussion occurs
• Months later another maintainer submits a new merge request for the same issue

Evidence

A maintainer marked it as a draft. The comment said that a quick check showed signs the merge request was AI-produced, and that it was being set aside "in order to avoid spending review time for AI nonsense."

Source

The next day, the contributor closed the merge request. They also closed a second, much smaller fix they had opened the same day, which nobody had raised any concern about.

Source

It was a real fix for a real problem. The page got its data from a list of satellites that made a separate database query for every single satellite, just to check one flag. The change replaced those thousands of queries with one.

Source