Skip to content
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

Review each commit separately doesn't always correspond to PR commits #479

Closed
marun opened this issue May 31, 2017 · 5 comments
Closed

Review each commit separately doesn't always correspond to PR commits #479

marun opened this issue May 31, 2017 · 5 comments

Comments

@marun
Copy link

marun commented May 31, 2017

When reviewing kubernetes/kubernetes#46527, I wanted to review only one of its 2 commits since I had reviewed the other commit in a different PR. I attempted to use 'Review each commit separately' but the first set of unreviewed diffs included changes from both commits. Is this working as expected? I've been having to fall back to using github reviews in cases like this, and I'd really prefer to be able to use reviewable.

cc: @thockin

@pkaminski
Copy link
Member

Hey Maru, looking at https://reviewable.kubernetes.io/reviews/kubernetes/kubernetes/46527 it appears that each revision holds just one commit (r1 is a37c004 and r2 is bab423e), so that part seems to be working fine. Is the issue that the automatically selected diff when you loaded the review was ⊥..r2 instead of ⊥..r1? If so, it's worth investigating why this happened, but an easy workaround in the meantime is to manually select the diff you'd like (e.g., r1..r2).

@pkaminski
Copy link
Member

Ping?

@marun
Copy link
Author

marun commented Jul 24, 2017

How do I choose an arbitary diff like r1..r2? The latest revision seems to always be selected (i.e. [chosen revision]..[latest revision]).

@pkaminski
Copy link
Member

You drag out a rubber band between the two revisions of interest. (You can find this tip in the pop-up help you get when you hit F1 on any revision strip.)

@marun
Copy link
Author

marun commented Jul 25, 2017

Ok, works for me.

@marun marun closed this as completed Jul 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants