Unable to resolve outdated conversations and merge

[TonyArra]

Is anyone else having this issue over the last week or two?

We have the option enabled to block merging a PR when there are unresolved conversations. Recently, if a conversation becomes outdated due to a new commit, I am unable to resolve the conversation unless I was the one to make the initial comment.

The creator of the PR and other members of the team are no longer able to see the conversation, but the PR is prevented from merging due to there being "unresolved" conversations

[pablomusumeci]

I'm experiencing the same issue. @TonyArra Have you found any work-around for unblocking the PR with outdated comments?

Edit: This is a duplicate of #10592. I managed to find and resolve the unresolved conversation by scrolling through the entire PR. So there is a way of unblocking the merge but it's just bad UX from Github.

[ibober]

I have the same issue with this PR
KhronosGroup/glTF#1977
It says there are 4 unresolved conversations, but I can't find them, really, how I should do this?
Also before some of them disappeared, I noticed that there were conversations that I couldn't resolve - no resolve button.

[aquanow-eric]

Turns out I need to click a button to load all conversations ... once that happens I can get at it and resolve.

[kopax-polyconseil]

That's when conversation still exist and have not been overriden by a force push, and then you are stuck!

[andreieftimie]

That's when conversation still exist and have not been overriden by a force push, and then you are stuck!

Any solution when this happens?

[andreieftimie]

That's when conversation still exist and have not been overriden by a force push, and then you are stuck!

Any solution when this happens?

Managed to find them in the Conversations tab.

[xbtmatt]

Make sure to unhide all hidden items. Couldn't find a conversation because it was lost due to a rebase and the commit disappearing from the repo until I just hit the unhide button for all items (not conversations, although it was a conversation that was hidden...)

[pmanole-volvocars]

Same here in 2025.

Clicked View:

Got here, but cannot find it, and the dropdown doesn't have the caret!

[walangitan]

Managed to find the unresolved conversation by manually finding it in the main pull request body. The link in the conversations tab did not work.

[bedrich-schindler]

Problem persists. In this pull request, it shows unresolved conversations:

But when I tried to open it, it shows:

I also can't find it in the file itself as it was removed with squash/force-push. This results in inability to merge pull request.

[vyvo2412]

I'm having this issue as well. Clicking 'Unresolved conversations' does not take me anywhere.

[ricardobeat]

Also having this issue right now blocking a PR merge.

In my case, the unresolved comments were on commits that have been removed by a rebase.

[qweered]

Same issue, cannot resolve my threads in nixpkgs repo

[rafaelbeckel]

I had this issue today, and it turns out there was a HIDDEN conversation in one of the collapsed blocks. If you're facing this, most probably you should painstakingly open them all until you find it.

It's still a bug, though, unresolved conversations should not be collapsible.

[rafaelbeckel]

I faced this issue again, this time it's a stale comment over a commit that do not exist anymore after rebase (branch was force-pushed), but GitHub still flags the comment as unresolved and blocks the merge.

[rafaelbeckel]

These are the commands that solved it:

gh api graphql -f query='query($owner:String!, $repo:String!, $pr:Int!){ repository(owner:$owner, name:$repo) { pullRequest(number:$pr) { reviewThreads(first: 100) { nodes { id isResolved comments(first: 50) { nodes { id url author { login } } } } } } } }' -F owner='YOUR_ORG_NAME' -F repo='YOUR_REPOSITORY' -F pr=80 | jq -r '
  .data.repository.pullRequest.reviewThreads.nodes
  | map(select(.isResolved==false))
  | map(select([.comments.nodes[].author.login] | any(test("copilot"; "i"))))
  | [ .[] | [.id, ([.comments.nodes[].author.login] | unique | join(","))] | @tsv ]
  | if length==0 then "NONE" else .[] end
'
PRRT_kwDOPU1kOs5d0RI2	copilot-pull-request-reviewer <--- the culprit

owner='YOUR_ORG_NAME'; repo='kyoso-YOUR_REPOSITORY'; pr=80;
ids=$(gh api graphql -f query='query($owner:String!, $repo:String!, $pr:Int!){ repository(owner:$owner, name:$repo) { pullRequest(number:$pr) { reviewThreads(first: 100) { nodes { id isResolved comments(first: 50) { nodes { author { login } } } } } } } }' -F owner="$owner" -F repo="$repo" -F pr=$pr | jq -r '
  .data.repository.pullRequest.reviewThreads.nodes
  | map(select(.isResolved==false))
  | map(select([.comments.nodes[].author.login] | any(test("copilot"; "i"))))
  | .[].id
');
for id in $ids; do
  gh api graphql -f query='mutation($id:ID!){ resolveReviewThread(input:{threadId:$id}) { thread { id isResolved } } }' -f id="$id" >/dev/null && echo "Resolved $id";
done
Resolved PRRT_kwDOPU1kOs5d0RI2 <--- DONE

[rayrayraykk]

Still exists.

[pietrofxq]

Facing the same problem. This one was caused by Copilot review

[ninikurshavishvili]

This appears to happen when review threads are attached to commits that no longer exist (force-push / rebase / squash), but GitHub still keeps the thread in an unresolved state.

A few things that helped in different cases:

UI workarounds (sometimes works):

Open the Conversations tab and use “Unhide all”

Scroll the entire PR timeline (including collapsed / outdated blocks)

Expand every collapsed diff — unresolved threads can live inside them

If the conversation is truly orphaned (no longer visible in UI):

The only reliable fix I’ve seen is resolving it via the GitHub GraphQL API using gh

This seems especially common with Copilot review comments, which can remain unresolved after rebases

Unfortunately, when the original commit is gone, the UI gives no way to resolve the thread — which feels like a GitHub bug rather than user error.

Would be great if GitHub either:

Auto-resolved threads when the target commit disappears, or

Exposed orphaned review threads clearly in the UI instead of blocking merges silently.

[dhisonp]

Still happening!

[sebastiancreatics]

Does anybody have a solution to this? @github please fix

[fedricantony]

Going through commit by commit helps me to resolve this issue. Here is what I did.

• Open the PR
• Go to the Commits tab
• Open each commit and check the diff
• Look for old unresolved comments
• Resolve them

[fedricantony]

Or look at the PR overview for outdated commit. Then go to that commit and resolve comments

[Alameen688]

There is a small conversation icon on the right section of the PR, click on it, and it will display unresolved comments.