-
Notifications
You must be signed in to change notification settings - Fork 605
Show changes since last review #363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It might be even more useful to be able to select the commits to review (because "changes since last review" sometimes does not work as expected + gets cleared once you open the changes on github). |
I can use this extension the first time I look at a PR, but after there are changes I can't. I don't need to re-review everything. I just need to review the changes since the last time I looked. Just being able to select which commits to use would solve this for me. |
To add on
and now that there is the The files that This behavior could be toggled by clicking |
Any update on this? This extension is really amazing but I think this is one of the key features that it's missing. |
Hi team, would like to bump this up. Would be very useful as re-reviewing a norm while doing a PR Code Review. |
+1 |
+1 💙 |
+1 please :-) |
@daviddossett, we are looking for two icons for switching between the ChangesSinceLastReview Mode and AllChangesOfPullRequest Mode. The icon will be placed in the panel in the top left (as in image) and when clicking it the Icon should be replaced with the second Icon, corresponding to switching into the other mode. Do you recommend using a specific icon pair or should new Icons be created for this case? |
@daviddossett it's more of a toggle. In effect, it will filter some of the files out, but also the contents of the files (really the diffs) will change. |
Ok, I'll see if we have any icons that work for this else I'll propose some new ones. |
@daviddossett I think these icons are a good starting point. The arrows (in pending) could possibly just be replaced with some symbol/icon which would indicate NEW changes (However, all changes are 'New' just some of them are since a review). A totally different option could be sort of a TODO list as changes since a review will probably be in relation to comments/suggestions made in that review. I'm looking forward to your suggestions. |
@daviddossett I'm worried that the |
This could work. One concern here would be that the dot icon pattern is typically used for a state that could be cleared. E.g. clicking on an icon with a dot would reveal something and then would remove the dot. Once reviewed, would this view still be visible? Or is it sort of temporary? This could make more sense if that's the case. Another option would be to use the "Modified" icon as the nested indicator: |
I prefer the first option as many of the other options also use a dot when there is something new and you could argue that the state will be cleared after reviewing the new changes. |
Conceptually it makes sense, but how would the interaction work? Would the icon with dot appear dynamically so that users notice it and click on it to view the new changes? I'd expect the dot to go away once reviewed. But then I wouldn't know what purpose the regular |
The Icon only appears when there is a change since a review, otherwise no icon appears. When there is a change since a review and a user clicks on the icon it will display only the changes since the review and the other icon (normal diff icon) appears to switch back to showing all changes. |
Ok, here's an idea to work with that:
Added new icons via vscode-codicons#124 |
These fit very well with how the interaction works. Thanks @daviddossett! |
GitHub.com flow
Blue line indicates there's a change:
Blue + indicates where I need to look from, handy link to the diff since I last looked:
Extension
No indication in tree (ie. I need to check notifications/email/github.com before switching back to extension):
No indication which commits/comments are new:
The text was updated successfully, but these errors were encountered: