Repository navigation
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
desrosj
added this pull request to stack #82877
September 14, 2026 18:31
desrosj
marked this pull request as ready for review
September 14, 2026 18:42
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @Copilot. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The focused change matches the upstream fix and correctly uses the pull request payload state.
Pull request overview
Restricts PR label enforcement to open pull requests, avoiding unnecessary runs on closed PRs.
Changes:
- Adds an open-state condition to the label enforcement job.
File summaries
| File | Description |
|---|---|
.github/workflows/enforce-pr-labels.yml |
Skips label enforcement when the pull request is closed. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
desrosj
removed this pull request from stack #82877
September 22, 2026 16:34
desrosj
changed the base branch from
fix-actions-6.9/remove-rn-workflows
to
wp/6.9
September 22, 2026 16:34
desrosj
force-pushed
the
fix-actions-6.9/simplify-pr-label-enforcement
branch
from
September 22, 2026 16:36
e72f615 to
7ff8872
Compare
|
Size Change: 0 B Total Size: 2.12 MB ℹ️ View Unchanged
|
desrosj
changed the base branch from
wp/6.9
to
fix-actions-6.9/fix-workflow-branch-filters
September 22, 2026 16:59
desrosj
added this pull request to stack #83392
September 22, 2026 17:00
…ch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
desrosj
removed this pull request from stack #83392
September 22, 2026 21:52
desrosj
changed the base branch from
fix-actions-6.9/fix-workflow-branch-filters
to
wp/6.9
September 22, 2026 21:52
desrosj
force-pushed
the
fix-actions-6.9/simplify-pr-label-enforcement
branch
from
September 22, 2026 23:24
7ff8872 to
9fe412a
Compare
desrosj
changed the base branch from
wp/6.9
to
fix-actions-6.9/fix-workflow-branch-filters
September 22, 2026 23:26
desrosj
added this pull request to stack #83413
September 22, 2026 23:26
desrosj
removed this pull request from stack #83413
September 28, 2026 15:44
…nit-js-date jobs.
…h-triggered tasks (`add-milestone`, `first-time-contributor-account-link`) both bail out immediately outside of `trunk`, so running them here on every push does nothing.
desrosj
removed this pull request from stack #83631
October 7, 2026 18:13
desrosj
changed the base branch from
fix-actions-6.9/fix-workflow-branch-filters
to
wp/6.9
October 7, 2026 18:14
desrosj
force-pushed
the
fix-actions-6.9/simplify-pr-label-enforcement
branch
from
October 7, 2026 18:16
08c7a08 to
f1a9529
Compare
desrosj
changed the base branch from
wp/6.9
to
fix-actions-6.9/fix-workflow-branch-filters
October 7, 2026 18:18
desrosj
added this pull request to stack #84190
October 7, 2026 18:19
desrosj
removed this pull request from stack #84190
October 8, 2026 21:14
desrosj
changed the base branch from
fix-actions-6.9/fix-workflow-branch-filters
to
wp/6.9
October 8, 2026 21:14
Member
Author
|
Closing: |
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
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.
Part of #82785.
What?
This cherry-picks the applicable change from d410e57 ("Only run label enforcement workflow on open PRs.", WordPress/gutenberg#76274) into this branch's own copy of
enforce-pr-labels.yml, addingif: ${{ github.event.pull_request.state == 'open' }}to thetype-related-labelsjob so the workflow no longer runs against closed PRs.This branch's
enforce-pr-labels.ymlalready has thepull_request_targettrigger andtypes:list that two of the three related trunk commits in this area introduced, so only this one line was actually missing here.Why?
Only running against open PRs avoids wasted/meaningless runs on PRs that are already closed.
Use of AI Tools
This PR was created by Claude Code under my supervision. All code should be treated as AI-produced and not yet reviewed by a human until this PR is marked Ready for Review.