devfile using sparseCheckoutDir in conjunction with a branch doesn't work right

[edeandrea]

Describe the bug

I'm using the CodeReady Workspaces thats part of the Red Hat developer sandbox (https://workspaces.openshift.com). I have a devfile in my project with a projects section that looks like this:

projects:
  - name: rhoar-getting-started
    source:
      type: git
      location: https://github.com/openshift-katacoda/rhoar-getting-started.git
      branch: solution
      sparseCheckoutDir: spring/spring-db-access

When the project gets checked out, the UI and the tooling (running git branch) shows master, yet the source code thats checked out reflects the correct branch (the solution branch in my specific case).

[che-bot]

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.

[svor]

/remove-lifecycle stale

[che-bot]

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.

[svor]

/remove-lifecycle stale

[ehsavoie]

i met a similar issue for a multi module maven project where each module is an example

[AObuchow]

@edeandrea @ehsavoie Unfortunately, sparseCheckoutDir has been removed from the Devfile API: devfile/api#128 (comment).

It probably makes sense to close this issue as such, unless there are other concerns/questions about this topic.

[AObuchow]

i met a similar issue for a multi module maven project where each module is an example

If your issue does not involve spareCheckoutDir, please open a new issue 🙏

[AObuchow]

FWIW, even though sparseCheckoutDir is no longer part of the Devfile API, it is currently being implemented as a project attribute. Relevant PR.

[che-bot]

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.