snapcraft checks only default branch for submodules
Bug #1999219 reported by
Ilya Fedin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Let's say we have a repository that has a folder with a dependency on it's default branch, but on the required branch/commit it's no more a folder, but a submodule. Expected behavior is to pull this submodule, but snapcraft pulls only those existing on default branch. I specify the commit using source-commit and source-depth: 1.
Revision history for this message
| Callahan Kovacs (mr-cal) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → Confirmed |
To post a comment you must log in.
Confirmed. I was able to reproduce this behavior with a core 20 and a core22 snap.