ci: stop Dagger from shallow-cloning the working tree#947
Merged
Conversation
In GitHub Actions pull request builds, Dagger's telemetry git-label collection runs `git fetch --depth 1` against the working tree whenever GITHUB_REF is a refs/pull/ ref, which turns the checkout into a shallow clone. Once shallow, `git merge-base origin/main HEAD` finds no common ancestor and the commitlint task (--from=origin/main) fails on every pull request. Most dagger invocations already prefix GITHUB_REF= to suppress this; a few were missing it. Prefix the remaining calls so Dagger never shallow-fetches the host repository. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
dosubot
Bot
added
the
size:XS
mnencia
changed the title
gbartolini
approved these changes
Jun 7, 2026
leonardoce
approved these changes
Jun 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In GitHub Actions pull request builds, Dagger's telemetry git-label collection runs
git fetch --depth 1against the working tree whenever GITHUB_REF is a refs/pull/ ref, which turns the checkout into a shallow clone. Once shallow,git merge-base origin/main HEADfinds no common ancestor and the commitlint task (--from=origin/main) fails on every pull request.Most dagger invocations already prefix GITHUB_REF= to suppress this; a few were missing it. Prefix the remaining calls so Dagger never shallow-fetches the host repository.
Upstream Dagger bug: dagger/dagger#13351