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

Update VS Code extension che4z-explorer-for-endevor to v1.1.0 #1264

Merged
merged 1 commit into from
Apr 13, 2022

Conversation

roman-kupriyanov
Copy link
Contributor

Signed-off-by: Roman Kupriyanov roman.kupriyanov@broadcom.com

What does this PR do?

Updates the version Explorer for Endevor in the registry.

Explorer for Endevor v1.1.0 change log:

  • Added the generate an element with copyback and generate with no source features.
  • Added the Signout-overriding functionality to the generate an element feature.
  • The Remove profile context menu item is changed to Hide profile to avoid confusion.
  • Now multiple notification messages are displayed in one message upon successful element generation.
  • Changed the VS Code version requirement. Ensure that you use VS Code 1.58.0 or higher.
  • Fixed an issue with the signout error recovery attempt when an element is edited and uploaded into a different location.
  • Fixed an issue that prevented the extension from updating an Endevor map tree after uploading the edited element into a new location.

Screenshot/screencast of this PR

What issues does this PR fix or reference?

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Signed-off-by: Roman Kupriyanov <roman.kupriyanov@broadcom.com>
@openshift-ci
Copy link

openshift-ci bot commented Apr 13, 2022

Hi @roman-kupriyanov. Thanks for your PR.

I'm waiting for a eclipse-che member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-actions
Copy link

Click here to review and test in web IDE: Contribute

@benoitf
Copy link
Contributor

benoitf commented Apr 13, 2022

/ok-to-test

@openshift-ci
Copy link

openshift-ci bot commented Apr 13, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: benoitf, roman-kupriyanov

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@benoitf benoitf changed the title Update VS Code extension che4z-explorer-for-endevor to v1.1.0 feat: Update VS Code extension che4z-explorer-for-endevor to v1.1.0 Apr 13, 2022
@benoitf benoitf merged commit 1b26e25 into eclipse-che:main Apr 13, 2022
@che-bot che-bot added this to the 7.47 milestone Apr 13, 2022
@roman-kupriyanov roman-kupriyanov deleted the e4e-1.1.0 branch April 14, 2022 08:05
@l0rd l0rd changed the title feat: Update VS Code extension che4z-explorer-for-endevor to v1.1.0 Update VS Code extension che4z-explorer-for-endevor to v1.1.0 Apr 21, 2022
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes ok-to-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants