Allow namespaces to require preference configurations for their subordinates.

Release notes

Preferences can be kept up-to-date in repositories subordinate to a namespace, whether that be a group or user, by defining them in the group or user's preferences.

Problem to solve

Namespaces, whether users or groups (and, therein, organisations, teams, and individual projects) cannot inherit preferences from their superordinates. They are able to inherit defaults, but this is inequivalent, because when those defaults are modified, the modification must be manually applied to all repositories via the GitLab API. ¹

Proposal

Permit preferences to be federated from a namespace to a repository. In practice, this may mean that a user federates their default repository preferences to all of their repositories, because they are solely for their own usage, thereby not requiring individualised preferences (excepting branding, like name and avatar, etcetera).

MediaWiki's official "Global Preferences" extension provides an example of this in practice: ^{2 3}

Links/References

This affects:

1. issues/419013 and

2. issues/571342

If implemented, this would replace:

1. issues/26540 and

2. its dependent issues/1180.

1. forum.gitlab.com/t/104327/2 ↩

2. mediawiki.org/w/index.php?title=Extension:GlobalPreferences ↩

3. meta.wikimedia.org/w/index.php?title=Community_Tech/Global_preferences ↩