Today's scripting doesn't look at changes in the kconfig dependency tree or the config definitions. This would be an additional analysis that should occur when considering what has changed.
REcently this tool https://github.com/alessandrocarminati/kconfig- was created which can map out kconfig trees. The backend code might expose enough meta data to use as an example to build a analysis engine for change impact of configuration.
Today's scripting doesn't look at changes in the kconfig dependency tree or the config definitions. This would be an additional analysis that should occur when considering what has changed.
REcently this tool https://github.com/alessandrocarminati/kconfig- was created which can map out kconfig trees. The backend code might expose enough meta data to use as an example to build a analysis engine for change impact of configuration.