Forking Renovate, why re-open old config error issue, and why no config warning on Dependency Dashboard? #29132
Unanswered
HonkingGoose
asked this question in
Request Help
Replies: 1 comment 1 reply
-
In the old days we had a few incidents where Renovate kept making issues over and over, so I defaulted behavior to reopen/reuse the old issue to keep the noise lower. It's maybe time to instead stop the reopening |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
Other
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Forking Renovate, GitHub, do not know what version
Please tell us more about your question or problem
I commented on a PR on another repository to answer some questions from a user about their Renovate config:
The member of the repository asked me some more questions based on my comment:
I don't know the answer to two of their questions. So I'm asking them here:
forking-renovate bot edited on Dec 6, 2023
to aWARN: Package lookup failures
message, but no config error message.Luckily I managed to answer at least one of their questions. 🙃
Logs (if relevant)
No logs, as I don't have access to their logs
Beta Was this translation helpful? Give feedback.
All reactions