Configuration management
Summary
It's currently quite a pain to apply same rules on many repos (if not all repos), it really takes 5-10 mins to make settings consistent for roughly 20 repositories. Some configuration management that saves this time should be implemented. This also aids consistency across different projects.
Proposal
There are multiple possibilities here, but I think this one would work best:
Supply another section, called "Configuration Management", where you can create, name and configure repo-configurations like you would see them on a repo. Repo's can either have their own independent config, or, there's another field where you can select configurations you've created in your "Configuration Management"-section. Once such a config is selected, editing only-repo configs is not possible(1), and changes in the configuration done inside the "Configuration Management" page reflect immediately inside all repos where the config is active.
(1) Advanced strategies could be maybe implemented that allow overrides. So the priority is: "Configuration Management"-config is loaded first and after that the repo-specific config is applied overriding values. Could be done in another iteration.