chore: allow Renovate to create new config warning issues #3662
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.
Summary
configWarningReuseIssue
tofalse
.Old behavior: Renovate re-opens a old config warning issue.
New behavior: Renovate creates a new config warning issue.
Read the Renovate docs,
configWarningReuseIssue
config option to learn more.More context
@ianlewis mentioned they want Renovate to create a new issue instead of re-opening an old one:
Here's an example of a Renovate config warning issue that was re-opened by Renovate recently:
Testing Process
Checklist