Close the PR (merge, close, mark as draft — doesn't matter)
expected: top-level message gets updated with new state
actual: no change
If anyone then replies in the thread, everyone will see the new, latest state
Seems to be that the client caches the top-level message.
We may be able to fix this just by having the bot first update the top-level message, and then post the "PR was merged" message to the thread. This may satisfy the 2.ii.a condition, and thus work around the issue.
This seems to be a client issue.
Repro (maybe?)
Seems to be that the client caches the top-level message.
We may be able to fix this just by having the bot first update the top-level message, and then post the "PR was merged" message to the thread. This may satisfy the 2.ii.a condition, and thus work around the issue.