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.

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

Update more than 10 PRs in a run #261

Open
taobojlen opened this issue Apr 9, 2024 · 0 comments
Open

Update more than 10 PRs in a run #261

taobojlen opened this issue Apr 9, 2024 · 0 comments

Comments

@taobojlen
Copy link

We use this action to run daily and merge a PR that will cut a new release. We regularly get results like this:

2024-04-09T14:54:18.206Z INFO  Action result: [
  { mergeResult: 'skipped', pullRequestNumber: 5642 },
  { mergeResult: 'skipped', pullRequestNumber: 5521 },
  { mergeResult: 'skipped', pullRequestNumber: 5520 },
  { mergeResult: 'skipped', pullRequestNumber: 5517 },
  { mergeResult: 'skipped', pullRequestNumber: 5516 },
  { mergeResult: 'skipped', pullRequestNumber: 5637 },
  { mergeResult: 'skipped', pullRequestNumber: 5629 },
  { mergeResult: 'skipped', pullRequestNumber: 5635 },
  { mergeResult: 'skipped', pullRequestNumber: 5626 },
  { mergeResult: 'skipped', pullRequestNumber: 5636 }
]
2024-04-09T14:54:18.207Z INFO  More than one result, using  first result for action output

Where, even though we do have a PR that matches the conditions, nothing gets merged. It looks like this action limits itself to running on 10 PRs at a time. Is there a way to increase the MAX_PR_COUNT so all our PRs get evaluated when the action runs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant