---
title: "When two reviewers ask for opposite changes | Proofline"
description: "If a bot and a maintainer, or two bots, ask for opposite changes, follow the project's written convention or the person who owns the code."
url: https://proofline.sh/learn/ai-review-conflicting-reviewer-comments/
---

[Learning center](/learn/)

# When two reviewers ask for opposite changes

If a bot and a maintainer, or two bots, ask for opposite changes, follow the project's written convention or the person who owns the code. Then check the losing comment's factual claim anyway, and say in its thread which request you followed and why, so the comment reads as answered rather than ignored.

Code review The Proofline team November 22, 2026 4 min read

## Why automated reviewers end up on the other side

An AI reviewer usually reviews each push as a fresh diff. When the author does what a human reviewer asked, the bot sees the result without the conversation that led to it, and can report the requested change as a regression. Two bots reviewing the same pull request have the same blind spot toward each other. Neither knows what the other said or what the maintainers decided.

A conflict therefore has two separate questions in it. Which request does the project want followed? Is the factual claim in the other request true? The first decides the code. The second decides what you write in the thread, and whether anything needs a follow-up.

## A maintainer and Copilot on a deprecation removal

In November 2026, a Home Assistant pull request removed the Telegram bot's deprecated `target` parameter "together with its `migrate_chat_ids_in_target` repair issue." [Pull request](https://github.com/home-assistant/core/pull/190123) The first commit also added cleanup to setup that deleted any leftover `migrate_chat_ids_in_target_` issues from the issue registry. Copilot reviewed that commit and reported: "No active review issues remain for the removal of the Telegram bot's deprecated `target` parameter." [Copilot's first review](https://github.com/home-assistant/core/pull/190123#pullrequestreview-5743095799)

A maintainer objected to the cleanup: "I don't think this clean up is great to need in every integration that uses persistent issues." He added, "I'd prefer if we can handle that centrally somehow. I think we can leave this out for now." [Maintainer's comment](https://github.com/home-assistant/core/pull/190123#discussion_r4449325578)

The author removed the cleanup in a commit titled "Remove cleanup of leftover target issues" and replied in the same thread: "Less of a problem I'd guess since the user can (and probably will) resolve it." [Author's reply](https://github.com/home-assistant/core/pull/190123#discussion_r4451729845)

Copilot then reviewed the new commit and asked for the opposite. Its summary said setup "does not delete persistent `migrate_chat_ids_in_target_` issues" and that "cleanup and the regression test are still needed." [Copilot's second review](https://github.com/home-assistant/core/pull/190123#pullrequestreview-5748269536) The maintainer approved, and the pull request merged on 3 November 2026 without the cleanup.

## Check the claim you did not follow

Following the maintainer was the right call for the code: he set the project's direction, and his objection was about a pattern across integrations, which a reviewer of one diff cannot weigh. Copilot's factual claim still deserved a check, because it describes what users would see after upgrading.

It holds. The deleted code created the issue with `is_persistent=True`, and the same pull request removed the issue's text from `strings.json`. [Pull request diff](https://github.com/home-assistant/core/pull/190123/files) Home Assistant's developer documentation says an issue "will be kept in the issue registry until it's removed by the integration that created it or by the user fixing it," and that a persistent issue "will be shown again to the user after a restart." [Repairs: issue persistence](https://developers.home-assistant.io/docs/core/platform/repairs/#issue-persistence) So users who had the repair issue before the upgrade can keep seeing it until they act on it.

The thread records this trade well. The maintainer named the reason, a cleanup pattern he did not want copied into every integration, and the author named the accepted cost, a leftover issue that users can resolve. What the thread does not record is a place for the central handling the maintainer wanted. The page links no follow-up issue. If the trade had needed revisiting, the issue the [guide to comments on unchanged code](/learn/ai-review-comment-on-unchanged-code/) describes, with an owner, would have kept it from depending on someone remembering this thread.

## Decide which request to follow

Work through these in order and stop at the first that applies:

1.  A written project rule covers the question: a contributing guide, a style guide, a linter configuration or an architecture decision. Follow it, and link it in the other thread.
2.  A maintainer or code owner has decided in this pull request. Follow them, and link their comment in the bot's thread.
3.  One request rests on a factual claim you can test, such as a crash, a leftover record or a syntax error. Run the test or read the reference, and follow the request the evidence supports.
4.  Two bots disagree and nothing above settles it. Pick the smaller change, and say that the choice was a judgment call.

Then answer the request you did not follow:

| What you find about its claim | What to leave in its thread |
| --- | --- |
| False | The evidence, as in [a dismissal reply](/learn/reply-to-dismiss-ai-review-comment/) |
| True, and the cost is accepted | The decision you followed and the cost, in one or two sentences |
| True, and someone should fix it later | The same, plus a linked issue with an owner |
| Already handled elsewhere | A link to the code or pull request that handles it |

The bot will review the next push too, and it may ask again for what you just removed, as Copilot did here. A repeated request is not new evidence. Answer it by linking the decision you followed, and change the code back only if the new comment names a fact that the decision did not weigh.

## One month of free code review.

New organizations get one calendar month of hosted code review for private and public GitHub repositories. No card or cloud connection required. [Eligibility and fair-use terms](/free-code-review/).

[Start free with GitHub](https://proofline.sh/orgs/plan?offer=free_month)

## Related reading

-   ### [A review comment on code your pull request did not change](/learn/ai-review-comment-on-unchanged-code/)
    
    Code review The Proofline team November 22, 2026 4 min read
    
-   ### [Write a dismissal reply that someone else can check](/learn/reply-to-dismiss-ai-review-comment/)
    
    Code review The Proofline team November 22, 2026 5 min read
