fix: use git tag --no-column to prevent dbt deps breakage with columnar git output#12728
Open
claygeo wants to merge 2 commits into
Open
fix: use git tag --no-column to prevent dbt deps breakage with columnar git output#12728claygeo wants to merge 2 commits into
claygeo wants to merge 2 commits into
Conversation
Contributor
|
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
1 similar comment
Contributor
|
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
claygeo
added a commit
to claygeo/dbt-core
that referenced
this pull request
Mar 30, 2026
claygeo
force-pushed
the
fix/git-tag-no-column
branch
from
6db3ff8 to
563934c
Compare
claygeo
added a commit
to claygeo/dbt-core
that referenced
this pull request
Mar 30, 2026
claygeo
force-pushed
the
fix/git-tag-no-column
branch
from
563934c to
f4c2219
Compare
claygeo
added a commit
to claygeo/dbt-core
that referenced
this pull request
Mar 30, 2026
claygeo
force-pushed
the
fix/git-tag-no-column
branch
from
f4c2219 to
1768960
Compare
claygeo
added a commit
to claygeo/dbt-core
that referenced
this pull request
Mar 30, 2026
claygeo
force-pushed
the
fix/git-tag-no-column
branch
from
1768960 to
d495263
Compare
…ar git output When a user configures git with column.ui=always, git tag --list outputs tags in columnar format which dbt cannot parse, breaking dbt deps. Use --no-column to explicitly disable columnar output regardless of user git configuration. The --no-column flag has been available since git 1.7.11 (2012). Fixes dbt-labs#10381
claygeo
force-pushed
the
fix/git-tag-no-column
branch
from
d495263 to
de2221e
Compare
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
1 participant
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.
Problem
Fixes #10381
When a user configures git with
column.ui=always(or any columnar output setting),git tag --listoutputs tags in multi-column format. dbt'slist_tags()splits by newline and gets garbled tag names, breakingdbt deps.Fix
Replace
git tag --listwithgit tag --no-columnincore/dbt/clients/git.py. The--no-columnflag explicitly disables columnar output regardless of user git configuration. Available since git 1.7.11 (2012).As suggested in the issue by @dbeatty10 (dbt maintainer).
1 line changed.