Fix GitConfigParser ignoring multiple [include] path entries#2100
Merged
Byron merged 1 commit intogitpython-developers:mainfrom Feb 14, 2026
Merged
Conversation
When an [include] section has multiple entries with the same key (e.g. multiple 'path' values), only the last one was respected. This is because _included_paths() used self.items(section) which delegates to _OMD.items(), and _OMD.__getitem__ returns only the last value for a given key. Fix by using _OMD.items_all() to retrieve all values for each key in the include/includeIf sections, ensuring all paths are processed. Fixes gitpython-developers#2099
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes a bug where GitConfigParser only respected the last path entry when multiple path values were specified under a single [include] or [includeIf] section. Git config allows multiple values for the same key (as documented in git help config), but GitPython was silently ignoring all but the last value due to using _OMD.items() which only returns the last value for each key.
Changes:
- Modified
_included_paths()to use a new_all_items()helper that calls_OMD.items_all()to retrieve all values for duplicate keys - Applied the fix to all four include scenarios: basic
[include], and[includeIf]with gitdir, onbranch, and hasconfig conditions - Added comprehensive test coverage for multiple path entries under a single
[include]section
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| git/config.py | Added _all_items() helper function and updated all four call sites in _included_paths() to use it instead of self.items() |
| test/test_config.py | Added test_multiple_include_paths_with_same_key to verify multiple path entries are all processed correctly |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
|
Thanks a lot, it's much appreciated. |
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.
Problem
When an
[include]section has multiple entries with the same key (e.g. multiplepathvalues), only the last one was respected:Only
my-configwould be included. This is valid git config pergit help config:Root Cause
_included_paths()usedself.items(section)which delegates to_OMD.items(). The_OMD.__getitem__method returns only the last value for a given key, so duplicate keys (like multiplepathentries) were lost.Fix
Use
_OMD.items_all()to retrieve all values for each key in include/includeIf sections, ensuring every path is processed.Test
Added
test_multiple_include_paths_with_same_keythat creates a config with twopathentries under a single[include]section and verifies both included files are loaded.Fixes #2099