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]

I am getting the same issue. Any workarounds?

[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!