Repository navigation
Display the merged configuration on the Dependency Dashboard #38024
beisenherz
started this conversation in
Suggest an Idea
Replies: 2 comments 4 replies
|
yes! upvote! |
0 replies
|
I agree that exposing to users what your final configuration is would be very useful! Via #39314 (this comment in particular), one of the difficulties with this is what we do with i.e. I wouldn't want us to enable this on the Dependency Dashboard, due to the size, and how that'll affect other Platform limits Would having this DEBUG log level help with this, in part? |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
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.jsonor 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.
All reactions