You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure this is a popular practice to use blobless clones on developer machines, so this is likely not a use case for EGit.
But for other use cases where JGit is used on CI/CD platforms (Jenkins, Maven, Sonar, ...) it would be great to support this feature.
Alternatives considered
The current alternative is to ask users to not use blobless clones, or to stop using JGit and use the native Git CLI.
We are noticing these issues in our Projects using CircleCI and SonarCloud. We would greatly appreciate support for this in the future without workarounds 👍
Description
Blobless clones are a suggested optimization to clone large repositories.
git clone --filter=blob:none <url>
The native Git CLI will lazy load blobs on-demand, but JGit simply fails:
Motivation
I am not sure this is a popular practice to use blobless clones on developer machines, so this is likely not a use case for EGit.
But for other use cases where JGit is used on CI/CD platforms (Jenkins, Maven, Sonar, ...) it would be great to support this feature.
Alternatives considered
The current alternative is to ask users to not use blobless clones, or to stop using JGit and use the native Git CLI.
Additional context
https://community.sonarsource.com/t/missing-blob-jgit-error-with-sonarcloud/109574
https://community.sonarsource.com/t/scan-on-git-blobless-clone-failed/106038
The text was updated successfully, but these errors were encountered: