Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: allow Renovate to create new config warning issues #3662

Merged
merged 1 commit into from
May 17, 2024

Conversation

HonkingGoose
Copy link
Contributor

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 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

  • Manually reviewed configuration change

Checklist

  • Review the contributing guidelines
  • Add a reference to related issues in the PR description.
  • Update documentation if applicable.
  • Add unit tests if applicable.
  • Add changes to the CHANGELOG if applicable.

Set `configWarningReuseIssue` to `false`.

Old behavior: Renovate re-opens a old config warning issue.

New behavior: Renovate creates a new config warning issue.

[Renovate docs, `configWarningReuseIssue` config option](https://docs.renovatebot.com/configuration-options/#configwarningreuseissue)

Signed-off-by: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Copy link
Collaborator

@ramonpetgrave64 ramonpetgrave64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks

@ramonpetgrave64 ramonpetgrave64 enabled auto-merge (squash) May 17, 2024 15:58
@ramonpetgrave64 ramonpetgrave64 merged commit 0d22a38 into slsa-framework:main May 17, 2024
75 checks passed
@HonkingGoose HonkingGoose deleted the patch-1 branch May 17, 2024 18:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants