-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Files in .vscode and .che folders of a git repository are ignored at workspace creation #21635
Comments
I think it happened after this PR into the repo https://github.com/eclipse-che/che-theia. |
Due to all the tests in devworkspace-handler are passed, I think the problem might be something else. |
It looks like I found cause of the problem. When the user create a workspace from git repository, dashboard tries to fetch It becomes much clear when trying to open the URL in the new tab I tried to get other files from git repository and was able to get file content when the file or directory name do not contain dot at the beginning. There is a potential place in che-server to fix the bug |
Might be a related issue #21639 |
Describe the bug
All defined plugins from the extensions.json are not installed If create a workspace by the factory and che-theia editor.
Also I see that the tools component doesn't contain environment variables that should be injected by the Dashboard:
It's also not possible to customize an editor by using
.che/che-editor.yaml
file:Che version
next (development version)
Steps to reproduce
/plugins
folder doesn't existExpected behavior
/plugins
folder should be existed and plugins from the .vscode/extensions.json should be installedRuntime
OpenShift
Screenshots
Installation method
chectl/next
Environment
Linux
Release Notes Text
Files in
.vscode
and.che
subfolders need to be processed during workspace creation as they can contain important workspace details (as the editor and the che-theia plugins to pre-install) but were ignored in recent versions due to a regression. This has been fixed in this release.The text was updated successfully, but these errors were encountered: