-
Notifications
You must be signed in to change notification settings - Fork 61
-
Notifications
You must be signed in to change notification settings - Fork 61
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
remove sparseCheckoutDir #128
Comments
from meeting: |
sleshchenko
added
the
area/api
Enhancement or issue related to the api/devfile specification
label
Mar 25, 2021
@kadel can we close this issue? |
Done |
This was referenced Jun 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, it is defined as
As I understand this, if I have a repo with a structure like this.
and I do
sparseCheckoutDir: dir2
I should end up with directory with/file2.txt
.Problem is that this is not how git sparse checkout works, and as far as I know, you can never clone the repo like this.
The way how sparse checkout in git works is that it can populate only certain directories, but the directory structure remains.
For example, If I have a repo with the above structure and I want to do sparse checkout if a
/dir2
I would end up with a directory structure like this:But what we want to do here is to end up with
/file2.txt
and that is not what sparse checkout does.I would actually consider completely removing this field from Devfile, It will create a lot of confusion and problems.
The text was updated successfully, but these errors were encountered: