Set vcs status marker only for resource related editor tabs#10534
Merged
RomanNikitenko merged 1 commit intomasterfrom Jul 27, 2018
Merged
Set vcs status marker only for resource related editor tabs#10534RomanNikitenko merged 1 commit intomasterfrom
RomanNikitenko merged 1 commit intomasterfrom
Conversation
Signed-off-by: Roman Nikitenko <rnikiten@redhat.com>
RomanNikitenko
added
kind/bug
Member
Author
|
ci-test |
Contributor
|
ci-test build report: |
vparfonov
approved these changes
Jul 26, 2018
39 tasks
musienko-maxim
approved these changes
Jul 26, 2018
RomanNikitenko
removed
the
status/code-review
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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?
Set vcs status marker ONLY for resource related editor tabs.
For example, we should skip this step at opening command editor or effective pom.
What issues does this PR fix or reference?
the PR does not fix #10309 (we should investigate this one), but allows to avoid last two errors described here
Signed-off-by: Roman Nikitenko rnikiten@redhat.com