At a branch level diff, I like how plastic shows you de info about de commits or the entire branch, you have all the information about de files changed, merge ( only changes on source) merged with changes in your branch, you have all, that's great. But I think this is only useful on this scenario, when you want information about the branch.
I think a pull request ( code review) is a totally different scenario, As a code reviewer, I don't want to know details about the history of the branch, I just don't care, I want to know how the changes on this branch can affect to the branch from this one(the branch under review) began, info about merged files, that wasn't modified on the reviewed branch are just noise.
In addition, when you work on a modified code review, the code that's appears is the old one ( I think should be the new one, again I don't want the history, I want to see the actual state ( with an option to see the previous comments of this revision)
At a branch level diff, I like how plastic shows you de info about de commits or the entire branch, you have all the information about de files changed, merge ( only changes on source) merged with changes in your branch, you have all, that's great. But I think this is only useful on this scenario, when you want information about the branch.
I think a pull request ( code review) is a totally different scenario, As a code reviewer, I don't want to know details about the history of the branch, I just don't care, I want to know how the changes on this branch can affect to the branch from this one(the branch under review) began, info about merged files, that wasn't modified on the reviewed branch are just noise.
In addition, when you work on a modified code review, the code that's appears is the old one ( I think should be the new one, again I don't want the history, I want to see the actual state ( with an option to see the previous comments of this revision)