Commit 63307a4f8b9 for woocommerce
commit 63307a4f8b9eef327bb05e4558438d9202ff8493
Author: Brian Coords <bacoords@gmail.com>
Date: Tue Sep 1 14:09:11 2026 -0700
Remove PR release communication triage (#68242)
* removes comms triage from PR template and github actions
* removes release communications mention from skill preflight
diff --git a/.ai/skills/woocommerce-git-draft-pr/SKILL.md b/.ai/skills/woocommerce-git-draft-pr/SKILL.md
index aa08d73d59e..dceb5314324 100644
--- a/.ai/skills/woocommerce-git-draft-pr/SKILL.md
+++ b/.ai/skills/woocommerce-git-draft-pr/SKILL.md
@@ -30,7 +30,7 @@ From the dynamic context above (read full diffs only if the stat summary is ambi
- **Significance**: Patch (most common), Minor (new features), Major (breaking — rare)
- **Bug fix?** Look for issue refs in commits/branch name (e.g., `#12345`, `fix/issue-12345`)
- **UI changes?** Changes in `client/`, `templates/`, CSS/SCSS, JSX/TSX
-- **Plugin-affecting?** Code shipped to users = yes. CI/CD, workflows, tooling, docs = no. This drives the Milestone, Changelog, and Release Communication decisions in Step 3.
+- **Plugin-affecting?** Code shipped to users = yes. CI/CD, workflows, tooling, docs = no. This drives the Milestone and Changelog decisions in Step 3.
### 2. Gather Context
@@ -56,7 +56,6 @@ Extract issue/PR refs from commits and branch name:
- Plugin-affecting, no changelog files in the diff → tick `Automatically create` with Significance, Type, and a user-facing Message.
- Plugin-affecting with changelog files already in the diff → tick `does not require` with the Comment "Created manually."
- Not plugin-affecting → tick `does not require` with a Comment explaining why (e.g., "Internal tooling, not shipped to merchants").
-- **Release Communication**: tick `Feature Highlight` for user-visible features merchants will notice, or `Developer Advisory` for changes affecting extension/theme developers (hook signatures, deprecations, REST API field changes). Otherwise leave both unchecked. Make sure you surface to the human you are working with when you mark either of these as checked, and emphasize they need to review the posted draft after the automation to validate the output.
After filling, keep the template's HTML comments (`<!-- -->`) — they support PR automation and GitHub tests. Remove only unfilled placeholder lines that are actual visible placeholders (e.g., `Closes # .`, `Bug introduced in PR # .`).
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 83564e28c9b..f3c815389f6 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -115,28 +115,6 @@ Using the [WooCommerce Testing Instructions Guide](https://developer.woocommerce
</details>
-### Release Communication
-
-<!-- release-communication-section -->
-Select the release communication labels this PR needs:
-
-- [ ] **Feature Highlight** - For user-facing features (what changed, user impact)
-- [ ] **Developer Advisory** - For developer-facing changes (what changed, how to detect, actions needed)
-
-<details>
-<summary>When to use each?</summary>
-
-**Feature Highlight**: New features, UI changes, or improvements that merchants/store owners will notice.
-
-- Example: "New bulk editing for products", "Improved checkout performance"
-
-**Developer Advisory**: Breaking changes, deprecations, or changes that affect themes/plugins/extensions.
-
-- Example: "Hook signature change", "Deprecated filter", "REST API field removed"
-
-Selected labels are applied when the pull request is merged.
-</details>
-
### Use of AI Tools
<!--
diff --git a/.github/workflows/pr-release-communication-labels.yml b/.github/workflows/pr-release-communication-labels.yml
deleted file mode 100644
index 18904e82c6b..00000000000
--- a/.github/workflows/pr-release-communication-labels.yml
+++ /dev/null
@@ -1,46 +0,0 @@
-name: 'PR release communication labels'
-
-on:
- pull_request_target:
- types: [closed]
-
-concurrency:
- group: release-communication-labels-${{ github.event.pull_request.number }}
- cancel-in-progress: true
-
-jobs:
- apply-labels:
- name: Apply release communication labels
- if: |
- github.event.pull_request.merged == true &&
- (
- contains(github.event.pull_request.body, '[x] **Feature Highlight**') ||
- contains(github.event.pull_request.body, '[x] **Developer Advisory**')
- )
- runs-on: ubuntu-latest
- timeout-minutes: 5
- permissions:
- pull-requests: write
-
- steps:
- - name: Apply selected labels
- uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
- with:
- script: |
- const body = (context.payload.pull_request.body || '').toLowerCase();
- const labels = [];
-
- if (body.includes('[x] **feature highlight**')) {
- labels.push('feature highlight');
- }
-
- if (body.includes('[x] **developer advisory**')) {
- labels.push('developer advisory');
- }
-
- await github.rest.issues.addLabels({
- owner: context.repo.owner,
- repo: context.repo.repo,
- issue_number: context.issue.number,
- labels,
- });