From 0d22a386d5cb772b18a04681a55628571a2f70d2 Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Fri, 17 May 2024 18:01:52 +0200
Subject: [PATCH] chore: allow Renovate to create new config warning issues
 (#3662)

# Summary

- Set `configWarningReuseIssue` to `false`.

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](https://docs.renovatebot.com/configuration-options/#configwarningreuseissue)
to learn more.

## More context

@ianlewis mentioned they want Renovate to create a _new issue_ instead
of _re-opening_ an old one:

-
https://github.com/slsa-framework/slsa-github-generator/pull/3635#issuecomment-2116420633

Here's an example of a Renovate config warning issue that was re-opened
by Renovate recently:

- https://github.com/slsa-framework/slsa-github-generator/issues/404

## Testing Process

- Manually reviewed configuration change

## Checklist

- [x] Review the contributing
[guidelines](https://github.com/slsa-framework/slsa-github-generator/blob/main/CONTRIBUTING.md)
- [x] Add a reference to related issues in the PR description.
- [ ] Update documentation if applicable.
- [ ] Add unit tests if applicable.
- [ ] Add changes to the
[CHANGELOG](https://github.com/slsa-framework/slsa-github-generator/blob/main/CHANGELOG.md)
if applicable.

Signed-off-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
---
 renovate.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/renovate.json b/renovate.json
index aac36deb2e..38d5b75ca9 100644
--- a/renovate.json
+++ b/renovate.json
@@ -4,6 +4,7 @@
   "vulnerabilityAlerts": {
     "schedule": "* 0-4 * * *"
   },
+  "configWarningReuseIssue": false,
   "postUpdateOptions": ["gomodTidy", "gomodUpdateImportPaths"],
   "packageRules": [
     {