Skip to content

Create labeler workflow. - #2513

Merged
westonruter merged 5 commits into
WordPress:trunkfrom
Hug0-Drelon:fix-2484
Jun 19, 2026
Merged

Create labeler workflow.#2513
westonruter merged 5 commits into
WordPress:trunkfrom
Hug0-Drelon:fix-2484

Conversation

@Hug0-Drelon

@Hug0-Drelon Hug0-Drelon commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes #2484

Relevant technical choices

Using action/labeler pinned to v6.1.0 commit.
The labeler config file is put directly in .github/workflow directory, maybe not the best place.

Use of AI Tools

I used Cursor.
@github-actions

github-actions Bot commented Jun 4, 2026 •
edited
Loading

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Hug0-Drelon <hugod@git.wordpress.org>
Co-authored-by: westonruter <westonruter@git.wordpress.org>
Co-authored-by: mukeshpanchal27 <mukesh27@git.wordpress.org>
Co-authored-by: sarthak-19 <sarthak8858@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.
mukeshpanchal27
mukeshpanchal27 approved these changes Jun 4, 2026
View reviewed changes

@mukeshpanchal27 mukeshpanchal27 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice ✨
Comment thread .github/labeler-config.yml
@mukeshpanchal27 mukeshpanchal27 added Infrastructure Issues for the overall performance plugin infrastructure no milestone PRs that do not have a defined milestone for release [Type] Enhancement A suggestion for improvement of an existing feature labels Jun 4, 2026
@mukeshpanchal27

mukeshpanchal27 commented Jun 4, 2026

Copy link
Copy Markdown
Member

@westonruter This PR only addresses half of the issue. Could we open a separate PR for the Assign Milestone part, or would you prefer to handle both fixes in a single PR?
@westonruter westonruter mentioned this pull request Jun 8, 2026
Closed
sarthak-19
sarthak-19 reviewed Jun 12, 2026
View reviewed changes

@sarthak-19 sarthak-19 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM !
Comment thread .github/workflows/add-pr-labels.yml
Comment thread .github/workflows/add-pr-labels.yml Outdated
westonruter and others added 3 commits June 18, 2026 13:41
@westonruter @sarthak-19
Run workflow when new commits are pushed
8cea7ef 
Co-authored-by: Sarthak <69689387+sarthak-19@users.noreply.github.com>
@westonruter @sarthak-19
Limit labeler workflow to trunk
f515d9b 
Co-authored-by: Sarthak <69689387+sarthak-19@users.noreply.github.com>
@westonruter
Remove duplicate types key in add-pr-labels workflow
deb7b66 
The duplicate `types:` key was inadvertently introduced in 8cea7ef when
GitHub failed while applying a suggestion, nesting the event types under a
second `types:` mapping and making the workflow trigger invalid.
@westonruter westonruter mentioned this pull request Jun 18, 2026
Open
@westonruter

westonruter commented Jun 18, 2026

Copy link
Copy Markdown
Member

Could we open a separate PR for the Assign Milestone part, or would you prefer to handle both fixes in a single PR?

I've opened another issue to track the other improvements:
@westonruter
westonruter merged commit f531143 into WordPress:trunk Jun 19, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Infrastructure Issues for the overall performance plugin infrastructure no milestone PRs that do not have a defined milestone for release [Type] Enhancement A suggestion for improvement of an existing feature

4 participants

@Hug0-Drelon @mukeshpanchal27 @westonruter @sarthak-19