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:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request label workflow now runs the ChangesPull request label enforcement
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to Label enforcement is limited to open pull requests as intended, with no merge-blocking risk identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The focused condition correctly matches the stated goal and upstream change.
Pull request overview
Restricts PR label enforcement to open pull requests, avoiding unnecessary workflow runs after closure.
Changes:
- Adds an open-state condition to the label enforcement job.
File summaries
| File | Description |
|---|---|
.github/workflows/enforce-pr-labels.yml |
Skips label enforcement for closed pull requests. |
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
force-pushed
the
fix-actions-7.0/simplify-pr-label-enforcement
branch
from
September 14, 2026 01:49
c8a6296 to
7064ff9
Compare
desrosj
marked this pull request as ready for review
September 14, 2026 16:29
|
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 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. |
desrosj
changed the base branch from
fix-actions-7.0/remove-rn-workflows
to
wp/7.0
September 22, 2026 16:29
desrosj
force-pushed
the
fix-actions-7.0/simplify-pr-label-enforcement
branch
from
September 22, 2026 16:31
7064ff9 to
561da4e
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/add-workflow-concurrency
September 22, 2026 16:33
|
Size Change: 0 B Total Size: 7.61 MB ℹ️ View Unchanged
|
…ranch filter, so PRs opened against this branch still get fixed-issue assignment and first-time-contributor labeling.
desrosj
changed the base branch from
fix-actions-7.0/add-workflow-concurrency
to
wp/7.0
September 22, 2026 21:48
desrosj
force-pushed
the
fix-actions-7.0/simplify-pr-label-enforcement
branch
from
September 22, 2026 21:49
561da4e to
ca9351d
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/add-workflow-concurrency
September 22, 2026 21:51
…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
changed the base branch from
fix-actions-7.0/fix-workflow-branch-filters
to
wp/7.0
October 7, 2026 18:14
desrosj
force-pushed
the
fix-actions-7.0/simplify-pr-label-enforcement
branch
from
October 7, 2026 18:16
d01e646 to
9ae25dc
Compare
desrosj
changed the base branch from
wp/7.0
to
fix-actions-7.0/fix-workflow-branch-filters
October 7, 2026 18:17
desrosj
changed the base branch from
fix-actions-7.0/fix-workflow-branch-filters
to
wp/7.0
October 8, 2026 21:10
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 #82782.
What?
This cherry-picks d410e57 ("Only run label enforcement workflow on open PRs.", WordPress/gutenberg#76274) into this branch's own copy of
enforce-pr-labels.ymlso the workflow no longer runs against closed PRs.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.
Summary by CodeRabbit