Add experimental functionality for labelling PRs by their size #3218
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
There was a problem hiding this comment.
Pull Request Overview
This PR adds experimental functionality for automatically labeling pull requests by their size to help assess review difficulty. The implementation uses the sizeup-action to analyze PR changes and apply size labels (XS, S, M, L, XL, XXL) based on lines of code changed.
- Introduces a GitHub Actions workflow that triggers on PR events to automatically label PRs
- Configures six size categories with different thresholds and color-coded labels
- Excludes generated files and focuses scoring on meaningful code changes
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/workflows/label-pr-size.yml |
GitHub Actions workflow that runs the sizeup action on PR events |
.github/sizeup.yml |
Configuration file defining size categories, scoring formula, and file exclusions |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
github-actions
bot
added
size/S
mbg
reviewed
Oct 20, 2025
Comment on lines
+3
to
+10
| on: | ||
| pull_request: | ||
| types: | ||
| - opened | ||
| - synchronize | ||
| - reopened | ||
| - edited | ||
| - ready_for_review |
There was a problem hiding this comment.
We have other workflows with these (or mostly these) triggers. Could we add this as a job to e.g. pr-checks.yml?
There was a problem hiding this comment.
The PR checks also trigger on pull_request and workflow_dispatch. We could filter out those triggers with an if but I'm not sure of the benefit.
Co-authored-by: Michael B. Gale <mbg@github.com>
mbg
approved these changes
Oct 20, 2025
This was referenced Oct 24, 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.
Label PRs by their size to give a quick assessment of how difficult they might be to review.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Merge / deployment checklist