fix: workaround for strict not failing when using RENOVATE_CONFIG_FILE #770
Conversation
This file contains 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
|
Thank you for your contribution! |
|
📝 I didn't know that renovate-config-validator can accept configuration files via positional arguments. This accepts multiple files, meaning we don't need to use for loop in shell script to validate multiple files. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to #768
Verified strict now exits with a non-zero code so the action will fail if there is a migration.
The quoting was giving me issues so I changed it (verified with shellcheck).
Not sure about my change on the logic on when config files are passed or not, seemed like if one is passed the usual location could be skipped, but maybe that was intentional.