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.

Sign up for GitHub

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

Jump to bottom

Improve the visibility of the VS Code command to create a terminal in a DevWorkspace container #22086

Closed
l0rd opened this issue Mar 22, 2023 · 1 comment
Closed

Improve the visibility of the VS Code command to create a terminal in a DevWorkspace container #22086

l0rd opened this issue Mar 22, 2023 · 1 comment
Assignees
@RomanNikitenko
Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Milestone
7.64

Comments

@l0rd
Copy link
Contributor

l0rd commented Mar 22, 2023 •
edited

Is your enhancement related to a problem? Please describe

Today it's possible to open a terminal in one of the containers defined in the devfile using the command "Terminal: Create new Terminal to DevWorkspace container".

image

The feedback we get is that users are not aware of it and it's hard to find.

Describe the solution you'd like

Some improvements:

  • We should not use the term DevWorkspace because DevWorkspaces are not exposed to users: the label should be Terminal: Create New Terminal (Select a Container)
  • The command is not in the Terminal menu, we should add it there too

image
@l0rd l0rd added the kind/enhancement A feature request - must adhere to the feature request template. label Mar 22, 2023
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 22, 2023
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. area/editor/vscode Issues related to the Code OSS editor of Che and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 22, 2023
@l0rd l0rd mentioned this issue Mar 22, 2023
Closed
@RomanNikitenko RomanNikitenko self-assigned this Mar 27, 2023
@RomanNikitenko RomanNikitenko mentioned this issue Mar 27, 2023
Merged
@RomanNikitenko RomanNikitenko added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. labels Apr 3, 2023
@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 6, 2023
@l0rd l0rd added this to the 7.64 milestone Apr 6, 2023
@devstudio-release
Copy link

sync'd to Red Hat JIRA https://issues.redhat.com/browse/CRW-4187

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RomanNikitenko RomanNikitenko

Labels
area/editor/vscode Issues related to the Code OSS editor of Che kind/enhancement A feature request - must adhere to the feature request template. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.64
Development

No branches or pull requests
4 participants
@l0rd @RomanNikitenko @devstudio-release @che-bot