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

Multiroot workspace: project must appear in the project explorer when it was cloned by a command in terminal #19544

Closed
1 task done
vitaliy-guliy opened this issue Apr 8, 2021 · 2 comments
Assignees
Labels
area/plugins kind/bug Outline of a bug - must adhere to the bug report 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.

Comments

@vitaliy-guliy
Copy link
Contributor

Describe the bug

In the multiroot workspace projects only appear if they are described in the devfile.
If we create a simple workspace w/o projects and then open a terminal and clone any project by hands, this project will not be opened in the Exporer view.
The same we have when trying to clone a project by Git: clone command.

Workspace plugin handles adding of the project to the devfile when cloning them by hands.
It's a good candidate to handle file system changes and register newly cloned projects in /projects/che.theia-workspace

Che version

  • nightly

Steps to reproduce

  • Create workspace w/o projects

  • Open terminal, clone any project with git clone ...

  • Try to clone another project with Git: clone command from command palette.

  • Check the file system. Open a terminal and run ls /projects

Screenshots

Screenshot from 2021-04-08 18-42-58

@vitaliy-guliy vitaliy-guliy added kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. area/plugins labels Apr 8, 2021
@RomanNikitenko
Copy link
Member

duplicates #19101

@azatsarynnyy
Copy link
Member

I'm transferring the labels from the original issue #19101 (comment)

Setting label new&noteworthy and milestone DevWorkspace Integration STEP 2 as it blocks #19489

fyi @l0rd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/bug Outline of a bug - must adhere to the bug report 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
Development

No branches or pull requests

4 participants