CHE-1866: Fix wrong viewing of git compare #2106
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ok |
|
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/74/ |
|
OK for me |
|
Build # 79 - FAILED Please check console output at https://ci.codenvycorp.com/job/che-pullrequests-build/79/ to view the results. |
|
Build success. https://ci.codenvycorp.com/job/che-pullrequests-build/84/ |
JPinkney
pushed a commit
to JPinkney/che
that referenced
this pull request
Aug 17, 2017
CHE-1866: Fix wrong viewing of git compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Fix problem with wrong Git compare viewing.
What issues does this PR fix or reference?
#1866
Previous Behavior
Git compare didn't respect selected file in editor part or in project explorer
New Behavior
Git compare opens change list according to selected file in editor part or in project explorer
@azatsarynnyy @RomanNikitenko Please review