Evaluating size labels on PRs #629
Replies: 2 comments
-
Thanks for opening the discussion @bsmth ! Just want to mention we're trialling this as a possible help with pull requests and the process - it was something we had feedback on when we we're discussing large prs https://github.com/orgs/mdn/discussions/501 (not explicitly in that thread but iirc in the November community meeting) 👍 |
Beta Was this translation helpful? Give feedback.
-
After some testing, we ended up swapping out for a different GH action and we've landed the labeler in this PR: You can see it in action here: If there's any issues or feedback, feel free to let us know here or through the usual channels (GH issue, chat, etc.) Thank you! |
Beta Was this translation helpful? Give feedback.
-
Hi everyone 👋🏻 there's been a few requests for the team over the last few months to add
size
labels to pull requests, mainly for two reasons:We already have logic for labeling PRs by technology category based on file paths, so I have rolled it into the existing labeler workflow. Hopefully we will merge this shortly and see how it works for reviewers and contributors.
Update (Jan 30th '24):
Going with the following labels for
mdn/content
for now:Update: The labeler landed here:
Criteria for size labels:
I did not put too much thought into the size criteria for now, which initially looks like this:
Ignoring files:
I have set the ignore list to the following:
If anyone has opinions or feedback on this, you're welcome to share. If you think other files should be ignored, the format of labels (
size/xs
,size/s
,size/m
,size/l
,size/xl
) or the label diff size is not good for each label (FYI, see how k8s do it), feel free to share.Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions