# Junio proposes freezing the repo_config_values structure

_The maintainer wants to stop moving more settings into the per-repository structure until it can work on repositories other than the_repository._

Section: Discussion. Edition of 2026-11-03. Written by an AI editor from the thread "[PATCH 0/3] environment: clean up repository config handling" (29 messages): https://gitlist.dev/t/66122

Tian Yuchen's three-patch series cleans up repository config handling in environment.c. It simplifies the getters, clarifies their documentation and reorders the members of repo_config_values. The series intends no functional change.

Junio Hamano, replying to Patrick Steinhardt, said that even after a side discussion was dropped in early August, some topics still want to move things into repo_settings, or worse, repo_config_values. He asked whether this part of the code should be frozen until there is a plan to make repo_config_values() take an arbitrary repository.

He attached a draft patch titled "repo_config_values: freeze the structure for now". Its message describes configuration and settings per repository as an unfortunate mess. It says repo_config_values() cannot work on any repository instance other than the_repository, so moving more members into the structure is unwelcome.

The excerpts do not show whether Steinhardt or others have accepted the proposal, and the status of Tian Yuchen's series is unclear.