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.

Sign up for GitHub

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

Jump to bottom

Automerge PR should not be throttled #17160

Closed
ns-ggeorgiev opened this issue Aug 12, 2022 · 2 comments
Closed

Automerge PR should not be throttled #17160

ns-ggeorgiev opened this issue Aug 12, 2022 · 2 comments
Labels
duplicate This issue is closed as a duplicate of another issue status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@ns-ggeorgiev
Copy link
Contributor

What would you like Renovate to be able to do?

When a PR is set to be automerge it should not be blocked based on PRs limits for manual intervention PRs.

If you have any ideas on how this should be implemented, please tell us here.

This can be achieved in one of the following ways:

  1. automerge PRs can be considered with priority over the rest of the PRs. Being automergable, they will likely move faster and unblock the limit for the rest of the PRs
  2. automerge PTs can have their own independent limit
  3. automerge PRs may simply have no bounds and be created ignoring the limits.

Is this a feature you are interested in implementing yourself?

Yes
@ns-ggeorgiev ns-ggeorgiev added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels Aug 12, 2022
@rarkins
Copy link
Collaborator

rarkins commented Aug 13, 2022

Hi, I would like to consider this to be a duplicate of #10546, which is a more generic solution to the same problem. Can you jump over to that issue to discuss?

@rarkins rarkins closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2022
@HonkingGoose
Copy link
Collaborator

Duplicate of #10546

@HonkingGoose HonkingGoose marked this as a duplicate of #10546 Aug 13, 2022
@HonkingGoose HonkingGoose added the duplicate This issue is closed as a duplicate of another issue label Aug 13, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
duplicate This issue is closed as a duplicate of another issue status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rarkins @HonkingGoose @ns-ggeorgiev