Config validation: enforce top-level options #28300
Labels
core:config
Related to config capabilities and presets
priority-3-medium
Default priority, "should be done" but isn't prioritised ahead of others
status:in-progress
Someone is working on implementation
type:feature
Feature (new functionality)
Describe the proposed change(s).
Config options like
baseBranches
should only be configured at the root/top-level of a config, but we don't have an automated way to document and validate this.We already have a
parents
field in config options which is currently used to tie options to non-root objects likepackageRules
.I propose:
root
,top-level
, or.
Probably done later:
The text was updated successfully, but these errors were encountered: