Display the merged configuration on the Dependency Dashboard

[Sironheart]

Tell us more.

I've had several problems in the past, due to not being able to see the final configuration of that repository. Would it be a great benefit of having the merged configuration per repository available in the dependency dashboard?

How comes that I need this:
I have a central repository, which provides a general config, which provides the 90% solution for most teams. Teams are able to override parts of that configuration for THEIR global scope. Last but not least, within the repository there is also the option of a renovate.json or comparable.

Having three or more levels of nesting (depending on the solution, some companies are implementing) makes it hard to trace which setting might be overwritten.

[carlos-lehmann]

yes! upvote!