chore: get-regexp is deprecated#1253
Closed
Rudxain wants to merge 1 commit into
Closed
Conversation
spacewander
reviewed
May 18, 2026
Collaborator
spacewander
left a comment
There was a problem hiding this comment.
git config get raises the runtime requirement to Git 2.46+. The new git config subcommands were introduced with Git 2.46, while older supported/system Git versions, for example Apple Git 2.39.5, reject git config get --all --show-names --regexp ... with usage output.
Let's keep the old one. Does git have a plan to drop the get-regexp?
Contributor
Author
oh :(
According to v3.0 docs, not yet, so I guess this PR can be closed |
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
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.
According to the docs,
config --get-regexpis deprecated in favor ofconfig get --all --show-names --regexp, so I replaced all the occurrences I've found