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 raisesAssertionError for valid setups when the parser is initialized with a relative config path.

• What changed

  • Updated include resolution inGitConfigParser.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 intest/test_config.py to verify:
    • main config includespath = b
    • main config is opened via a relative path
    • included values are successfully loaded fromb

• Behavioral impact

  • Relative include semantics now align with git’s documented behavior even when the initial config path passed toGitConfigParser is relative.
  • Existing include cycle/seen-path handling remains unchanged.

# before: could raise AssertionError if main config path is relativewithGitConfigParser(os.path.relpath(main_cfg),read_only=True)ascr:cr.get_value("section","key")# now: relative include in main_cfg resolves correctly

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