Handle relative include.path when root config is provided as a relative path#2104

Copilot

Git config allows relative include paths to be resolved relative to the config file containing the directive. GitPython currently asserts the source config path is absolute during include resolution, which raises AssertionError for valid setups when the parser is initialized with a relative config path.

What changed
- Updated include resolution in GitConfigParser.read() to normalize the current config file path to absolute when needed before resolving relative includes.
- Removed the absolute-path assertion that caused valid relative-path configurations to fail.
Regression coverage
- Added a focused test in test/test_config.py to verify:
  - main config includes path = b
  - main config is opened via a relative path
  - included values are successfully loaded from b
Behavioral impact
- Relative include semantics now align with git’s documented behavior even when the initial config path passed to GitConfigParser is relative.
- Existing include cycle/seen-path handling remains unchanged.

# before: could raise AssertionError if main config path is relative
with GitConfigParser(os.path.relpath(main_cfg), read_only=True) as cr:
    cr.get_value("section", "key")

# now: relative include in main_cfg resolves correctly

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Initial plan

6c7843a

Copilot AI assigned Copilot and Byron Feb 25, 2026

Copilot started work on behalf of Byron February 25, 2026 08:29 View session

fix: resolve relative includes from relative config paths …

5938ae3

Co-authored-by: Byron <63622+Byron@users.noreply.github.com>

Copilot AI changed the title [WIP] Test and fix issue with GitPython functionality Handle relative include.path when root config is provided as a relative path Feb 25, 2026

Copilot finished work on behalf of Byron February 25, 2026 08:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Handle relative include.path when root config is provided as a relative path#2104