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

multiroot: Bi directional synchronization of workspace root definition with devfile #19368

Closed
sunix opened this issue Mar 23, 2021 · 1 comment
Closed

multiroot: Bi directional synchronization of workspace root definition with devfile #19368

sunix opened this issue Mar 23, 2021 · 1 comment
Labels
area/editors area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@sunix
Copy link
Contributor

sunix commented Mar 23, 2021 •
edited
Loading

Is your enhancement related to a problem? Please describe.

At the moment, multiroot is configured based on devfile definition, each project in a devfile is then convert into a workspace root.

Creating a git project in /projects is also updating the devfile. But it is not converting it to workspace root folder (unless we restart the workspace maybe)

Describe the solution you'd like

Maybe the missing piece is to convert any new git projects in /projects into a workspace root ? (trigger che-workspace file update when the devfile is updated)

This is part of #15529
@sunix sunix added the kind/enhancement A feature request - must adhere to the feature request template. label Mar 23, 2021
@sunix sunix mentioned this issue Mar 23, 2021
Closed
6 tasks
@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 23, 2021
@vzhukovs vzhukovs added status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. area/editors area/plugins and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Mar 23, 2021
@che-bot
Copy link
Contributor

che-bot commented Sep 20, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 20, 2021
@che-bot che-bot closed this as completed Oct 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/editors area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sunix @vzhukovs @che-bot