fix: use default config for config files#2108
Merged
Merged
Conversation
Ullaakut
approved these changes
Apr 17, 2026
Member
Ullaakut
left a comment
Ullaakut
left a comment
There was a problem hiding this comment.
Code SGTM, didnt read config file in testdata though
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the problem I am trying to address?
This uses the default config as the basis for config files, so new options being added get auto-defaulted in existing installations.
How is the fix applied?
Start with a default, go from there.
What GitHub issue(s) does this PR fix or close?
Fixes #