increase max_pull_requests to 250 #2681
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue This PR Addresses
Fixes #2645
Type of Change
Description
According to the build logs for Release 2.4.0, 220 merged PRs were accounted for.
The easiest fix is to increase the
max_pull_requests
option in therelease-changelog-builder-config.json
However, I have been trying, but have failed, to understand how it got to 220 merged PRs.
Trying to query merged PRs during the time frame provided by the log only comes up with 80 PRs
Querying for all closed PRs, not just merged, during this time frame comes up with 113 PRs.
Similar discrepancies are also in the Release 2.3.0 log where 152 merged PRs were accounted for. But querying on GitHub, there is only 48 merged PRs, and 60 closed.
I couldn't load logs for earlier releases to check.
I suspect, but am unsure if PRs from the merged forked repositories are being accounted for.
Checklist