Managing Rate-Limiting PR requests when there is also global setting present #34694
Unanswered
knuurr
asked this question in
Request Help
Replies: 1 comment
-
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Formatting your logsSelect me to read instructionsPlease put your logs in a
If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
A Mend.io-hosted app
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
We are using Mend Renovate Bot to manage dependency updates, and we need to enforce a limit of one open PR per update type (patch/minor/major) at a time for specific dependencies.
Current Issue:
Example of current configuration for n8n:
This was for n8n, but we also have global setting:
Desired Outcome:
Are there additional Renovate settings we should use to enforce this behavior?
For context Here is our current full Renovate configuration:
Click to expand JSON config
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions