^{Originally posted by felipecrs March 29, 2025}

Tell us more.

This is derived from this other discussion.

Currently, there is prHourlyLimit to help preventing overloading of CI machinery. That option will rate-limit the number of PRs created per hour, and helps a lot during onboard of new projects.

However, for projects which are already onboarded and has most of the PRs created already, this option will not help much.

For example, imagine the following configuration:

{
  "prConcurrentLimit": 50,
  "prHourlyLimit": 5,
  "rebaseWhen": "behind-base-branch"
}

This would create 5 PRs hourly and stopping when it reaches 50. When one of the PRs are merged, another one will be created, but all the other 49 will also be rebased in the same run, because there is no option to rate-limit the number of commits that can happen per hour.

When a PR is changed with new commits, the CI workflows will be triggered, and in this case, 50 workflows will be triggered, potentially causing CI overload.

It would be great if an option like commitsHourlyLimit was implemented. This option would supersede prHourlyLimit and would prevent Renovate from pushing new commits to existing PRs if they surpass the limit configured.

One implementation idea is to adjust the following code:

- return scm.commitAndPush({
+ const result = await scm.commitAndPush({
    baseBranch: config.baseBranch,
    branchName: config.branchName,
    files: updatedFiles,
    message: config.commitMessage!,
    force: !!config.forceCommit,
    platformCommit: config.platformCommit,
    // Only needed by Gerrit platform
    prTitle: config.prTitle,
  });
+
+ if (result) {
+    incCountValue('HourlyCommits');
+  }
+
+  return result;

From what I understand, this function only returns a value when the push operation successfully happened.