PR with [SECURITY]
title suffix still doesn't bypass PR rate limit
#31482
Unanswered
MPV
asked this question in
Request Help
Replies: 1 comment 1 reply
-
Hi there, A maintainer decided this is not a bug, and behaving as designed. The maintainer will explain why this behavior is correct. To avoid confusing future readers, we will close this Discussion. We want Bug-type Discussions to be about things that we rate as bugs. For more details, please read our development docs about bug handling. If this bug report makes you think of an idea for a new feature, or how to improve a current feature, feel free to create a new Suggest an Idea Discussion. Thanks, the Renovate team |
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?
I think I found a bug
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
I have a
renovate.json
that contains:Why does not a PR matching the last rule bypass the PR rate limit (10)?
See screenshot of the issue:
It sets the title as I'd expect it to, i.e. into:
Update ibm-semeru-runtimes:open-11-jdk-focal Docker digest to 259e122 [SECURITY]
However I'm also expecting it to bypass the PR rate limit, as described like this on
prConcurrentLimit
:Any ideas?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions