Closed yurishkuro closed 1 month ago
I added --unshallow
because without it the script didn't work when pointing jaeger-ui to a non-tagged commit. Didn't realize git complains if the repo is already unshallowed :|
the script didn't work when pointing jaeger-ui to a non-tagged commit
Seems to work fine for me when I removed --unshallow
. Perhaps your local repo had an issue with how the submodule was initialized.
It works locally, but not in CI. GitHub actions checks repos out as shallow by default. We do have git fetch --prune --unshallow --tags
in the workflow file to unshallow the repo, but afaics that only unshallows the root repository and not all submodules.
cc @andreasgerstmayr