-
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
Add keepDir support for Devfiles #13671
Comments
It may be related somehow to #13688 |
What was the goal of keepDir in Che6 ? is this still accurate with che-theia ? |
@sunix I believe that idea is quite simple and not related to che-theia or GWT idea. |
In my opinion this was needed only because we couldn't set a 'type' for a subfolder of a che6 project. |
This was related to the sparse checkout in the factories. Yes it is important. |
ok. let's do it but i would rename it sparse-checkout rather then keepDir old article (but still actual i guess) of how to achieve that with git: https://briancoyner.github.io/articles/2013-06-05-git-sparse-checkout/ |
@slemeur rethinking about this. For samples like the vertx ones, i think it would be better to clone all the repo and find a way to emphasize one of the samples by expanding it and opening files. Or just open a dedicated workspace root folder on the right sample. |
When I was playing with the sample devfiles, I encountered this same problem with the go samples. I thought about having generic build/test/run tasks that would get the sample to work with using task inputs (https://code.visualstudio.com/docs/editor/variables-reference#_input-variables) but alas, that doesn't seem to be supported by Theia yet (eclipse-theia/theia#5836). |
@skabashnyuk this is an ide2 task right ? |
another option to concider is to use workspace root |
It can be. |
just want to state that keepdir/sparsecheckout is a useful but separate feature from being able to just import/focus on a subset of bigger checked out project; which is why I opened #14550 |
@maxandersen yes this was what I intended to say there This issue is one proposal to solve a problem in a flow where the user would like to work on a specific subfolder of a bigger git project. I am not convince that sparse checkout is the way to go. |
correct - but sparse checkout is not a bad feature to have though. Having way to focus/limit import from a larger repo while still having it checked out would be of higher priority would I say as it applies to more usecases imo. |
In the Che 6 specification we have "projects": [
{
"source": {
"type": "git",
"location": "https://github.com/eclipse/che",
"parameters": {
"keepDir": "core",
"branch": "master"
}
}
}
] Format of project definition in devfile is slightly different. So the suggestion is to put the projects:
- name: che
source:
type: git
location: 'https://github.com/eclipse/che'
branch: 'master'
keepDir: 'core' @l0rd @skabashnyuk @evidolob @sleshchenko @mshaposhnik @mkuznyetsov is it ok for you? |
what does |
@maxandersen previously it used sparse checkout https://briancoyner.github.io/2013/06/05/git-sparse-checkout.html. Technically nothing is removed. |
could we rename |
We can give any name to the parameter, but the question is in meaningful name. Sparse checkout is a feature and having a directory for its value is weird as for me. I would expect a boolean value for parameter with such name...
IMO, keep directory works better. |
@mmorhun
it is just not to confuse users with another name.
This is the kind of question people will have if we name it |
maybe renamed it |
|
Done |
Che 6 factories used to support "keepDir" param to specify a subfolder of a project repository.
Devfile model currently does not support this.
To support it on Che side, it requires to change the model, schema, DB. For Che 7 Theia based workspaces, would require to add support for Theia as well.
The text was updated successfully, but these errors were encountered: