Customize the issue-labeler train workflow to specify a page size for pulls #11078
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
the
|
Learn Build status updates of commit 2c83c4f: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
gewarren
approved these changes
Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Support a pullPageSize in the train.yml composite workflow (dotnet/issue-labeler#97).
The train workflow is not able to successfully download the pull requests for this repo to feed the training. Likely because of how many files are involved in many PRs in this repo, the queries for fetching pull requests get increasingly slow with each page of data, and 25 pulls per page is timing out. Local testing revealed that any page size over 1 is likely to time out quite a bit.
The reusable
train.ymlworkflow from issue-labeler does not currently support an input parameter for the page sizes, let alone different page sizes for issues and pulls. To work around this, the logic from that reusable workflow is decomposed directly into this repo's workflow so the page size can be specified to the Downloader. The functionality of the train job will remain the same overall.