You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: Drop product-area detection, just tag the caller's product name
Per-repo file-path -> product-area mapping was more granularity than
needed for a Slack pulse feed. The product field is now always the
calling repo's name (e.g. "Elementor" or "Elementor Pro"), passed as
a plain product-name input instead of a product-areas-file.
This removes the whole Product Area Detection section from the shared
prompt, drops the AI's product classification (and its validation),
and lets callers drop their per-repo areas file entirely.
Ref: ED-24831
Co-authored-by: Cursor <cursoragent@cursor.com>
Copy file name to clipboardExpand all lines: actions/product-pulse/action.yml
+7-11Lines changed: 7 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -5,8 +5,8 @@ inputs:
5
5
pr-number:
6
6
description: 'Pull request number to generate the pulse for'
7
7
required: true
8
-
product-areas-file:
9
-
description: 'Path (relative to the checked-out caller repo) to the repo-specific product-areas markdown file (PRODUCT_NAME/PRODUCT_AREAS/PRODUCT_ENUM). Combined with this action''s shared prompt-template.md to build the full prompt.'
8
+
product-name:
9
+
description: 'Product name to use in the prompt and Slack header (e.g. "Elementor" or "Elementor Pro")'
10
10
required: true
11
11
model:
12
12
description: 'Cursor Agent model to use for pulse generation'
Copy file name to clipboardExpand all lines: actions/product-pulse/prompt-template.md
+2-16Lines changed: 2 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,6 @@ Every included PR must also be classified with a `type`:
36
36
-`"improvement"` — makes an existing feature faster, smoother, or easier to use, without adding new capability
37
37
-`"internal"` — a notable change worth logging but with no direct end-user impact (e.g. new admin-only tooling)
38
38
39
-
## Product Area Detection
40
-
41
-
Based on which files the PR touches, determine the product area:
42
-
43
-
{{PRODUCT_AREAS}}
44
-
- If the PR touches multiple areas, pick the primary one (where the main feature lives).
45
-
- Changes in `packages/` belong to whichever product area consumes them — check the PR context.
46
-
47
39
## Output Format
48
40
49
41
Output ONLY valid JSON in this exact format:
@@ -52,7 +44,6 @@ Output ONLY valid JSON in this exact format:
52
44
{
53
45
"skip": false,
54
46
"type": "feature",
55
-
"product": "Widgets",
56
47
"title": "Loop Through WooCommerce Products",
57
48
"description": "You can now build dynamic product grids that automatically loop through your WooCommerce catalog. No more manually adding each product one by one."
58
49
}
@@ -67,8 +58,6 @@ Or if skipping:
67
58
}
68
59
```
69
60
70
-
The `product` field must be one of: {{PRODUCT_ENUM}}.
71
-
72
61
The `type` field must be one of: `"feature"`, `"fix"`, `"improvement"`, `"internal"`.
"description": "You can now drag widgets directly from one column to another in the editor. No more copy-paste or delete-and-recreate when rearranging your layout."
103
91
}
@@ -125,7 +113,6 @@ Why it's bad: The title doesn't tell users WHAT the feature does.
125
113
{
126
114
"skip": false,
127
115
"type": "feature",
128
-
"product": "Theme Builder",
129
116
"title": "Preview Templates Before Publishing",
130
117
"description": "You can now preview how a theme template looks against real content before making it live. Catch layout issues before your visitors do."
131
118
}
@@ -136,7 +123,6 @@ Why it's bad: The title doesn't tell users WHAT the feature does.
136
123
{
137
124
"skip": false,
138
125
"type": "fix",
139
-
"product": "Widgets",
140
126
"title": "Fixed Broken Icons in Nav Menu",
141
127
"description": "Custom icons in the Nav Menu widget no longer disappear when the Inline Font Icons experiment is off."
142
128
}
@@ -156,11 +142,11 @@ Why it's bad: The title doesn't tell users WHAT the feature does.
156
142
A PR titled `chore: update Playwright config` that only touches `.github/workflows/playwright.yml` and `tests/playwright/` → skip. CI and test infrastructure changes are never product-facing.
157
143
158
144
### Feature PR (include):
159
-
A PR that adds a brand-new user-visible widget or capability, touching paths matched in the Product Area Detection list above → include with the corresponding product. New user-visible widgets always qualify.
145
+
A PR that adds a brand-new user-visible widget or capability→ include. New user-visible widgets always qualify.
A PR that only bumps versions or updates a CHANGELOG.md under `packages/` → skip (release housekeeping).
163
-
A PR that changes behavior inside a `packages/` source directory with corresponding UI impact → include with the product area that consumes that package. Read the diff and PR body to determine whether the package change reaches users.
149
+
A PR that changes behavior inside a `packages/` source directory with corresponding UI impact → include. Read the diff and PR body to determine whether the package change reaches users.
0 commit comments