gh stack creates more force pushing which the review tool still does not handle properly

[mancusi]

Perhaps an orthogonal concern to gh stack but this is a situation that is run into more frequently using it.

Unlike tools like graphite or gerrit which manage reviews as a changeset and track the changes in commits a review refers to, force pushing a branch from commit a to commit b prevents you from reviewing changes from commit a to commit b.

This means having to re-review an entire change set when responding to comments instead of being able to view changes since your last review. Since branches are now force-pushed more frequently this makes it more frustrating to do PR reviews than before.

[mancusi]

The feedback here is connected to this long-running discussion thread https://github.com/orgs/community/discussions/3478