-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Introduce SCM Plugin-Api #4279
Introduce SCM Plugin-Api #4279
Conversation
hello @vinokurig It may help people to know which one you used and how it is working, etc. |
@@ -0,0 +1,187 @@ | |||
/******************************************************************************** | |||
* Copyright (C) 2018 Red Hat, Inc. and others. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2019, please review copyrights for new filws
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
Should not SCM extension provide SCM UI and not rely on git extension for it? |
@akosyakov It should provide UI, I think this is going to be done in the scope of #4171. The Scm Service doesn't relay on git extension, Git sends events to Scm Service. @benoitf The Api is needed for VsCode Git extension (eclipse-che/che#4266) but since there is no UI part for SCM Service yet, it is hard to test it in the current state. |
Reviewing... |
#4171 is just about menu contributions the description of #4103 says:
This PR does not seem to implement it yet. I'm fine doing migration via several PRs though. The issue should be resolved when git extension is completely refactored to work via scm extension. |
aa32ee9
to
8a4fd9a
Compare
Ok, I am going to continue with UI, but I think this can be merged as a part 1. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine, waiting approval from @kittaakos as he did a review
Thanks for the reminder, @benoitf. I will look into the changes once more when the DCO check and the builds are fine. |
20a5ba6
to
7f27542
Compare
@kittaakos The tests passed locally but they failed at travis-ci job |
Thank you for your patience, @vinokurig! I have looked into your changes, tried it locally with multiple repositories. It works, however, when I have three repositories in my workspace when I do a browser refresh and I take the heap dumb, I can see nine |
Thanks for checking, I will try once more. |
I could. Here are the steps:
I hope this helps to fix the leak. |
It is strange, but I couldn't reproduce your scenario, have you pulled the latest version? |
Yes. |
I'll give it a try once more... |
I'll record a video of my steps ASAP |
Signed-off-by: Nigel Westbury <nigelipse@miegel.org>
@benoitf done |
@svenefftinge is it ok on your side to merge this PR ? |
Signed-off-by: Igor Vinokur <ivinokur@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, sorry fr the delay. I thought it was already merged.
@vinokurig you did not address my comment #4279 (comment) @svenefftinge this PR lost changes from master, we have to revert or fix it asap |
I was not taliknig about VS Code exteniosn, but theia Git extenison. It is bogus now on master. Also you have not fixed menu items in the main menu. |
@@ -33,9 +33,8 @@ before(() => { | |||
}); | |||
|
|||
describe('theia left panel', () => { | |||
it("should show 'Explorer' and 'Git'", () => { | |||
it("should show 'Explorer'", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vinokurig, indeed. but why?
what's the reason to not show SCM?
I've randomly picked a commit from history for Git extension and it's turned out to be lost as well: @vinokurig please analyze changes to git extension done since you've started working on it and make sure that everything is recovered. |
@vinokurig, as pointed out by @akosyakov, there are missing changes. we should take a step back, revert this PR and improve it. |
Ok, I'll create a new PR with the changes |
could you clarify? would you revert for now? |
Is it possible to keep it and provide fixes ASAP? |
@vinokurig it has to be fixed beginning next week, since there are products and example apps relying on next version of git extension. I will help with analysis Monday morning, depending on how much is lost, we decide whether we revert or fix it on the same day. if @AlexTugarev @svenefftinge are not objecting, if you need git extension working as before today, then go ahead and revert. |
@akosyakov @AlexTugarev I've opened a PRs with fixes #5254, #5255, #5256, could you please tkae a look. Can we avoid revert SCM with those fixes? |
This PR contains:
#4103, #4666, #4266
VsCode Git Extension integration: