Don't allow Phabricator AI reviews on patches that have already landed

Open
#5,779 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
devtools

Research direction

Start by tracing the code path that allows an AI review to be requested for a Phabricator revision, using the linked D456 review as the reproduction. Done means requests are permitted for WIP or review-needed revisions but rejected once a patch has landed; check the relevant request-handling tests if present.

Written by the indexing model from the issue text.

Description

reviewhelper-api

I just received a notification from Phab of an AI review:

https://phabricator.services.mozilla.com/D456#9938008

This AI review is dated Mar 8 2026, 7:28 PM, this patch landed Jan 31 2018, 4:19 PM.

This is clearly the result of someone experimenting with the AI tool. Clearly there's no value in a review of a patch that landed 8 years ago; this just costs time and money.

Requesting an AI review should only be possible on revisions that are WIP or need review, not after they have landed.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 13h
Merged PRs (30d)
65

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.