Skip to content

Commit 3f096ff

Browse files
authored
fix: restrict community submission workflows to labeled event only (#2741)
Both add-community-preset and add-community-extension workflows previously triggered on issues opened, edited, and labeled events. This caused them to fire on every new issue and post noisy bot comments explaining the issue wasn't a submission (see #2739). Changes: - Narrow trigger from [opened, edited, labeled] to [labeled] only - Update prompt instructions to stop silently on non-matching issues instead of posting a comment
1 parent f50839a commit 3f096ff

4 files changed

Lines changed: 52 additions & 66 deletions

File tree

‎.github/workflows/add-community-extension.lock.yml‎

Lines changed: 22 additions & 24 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎.github/workflows/add-community-extension.md‎

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ emoji: "🧩"
44

55
on:
66
issues:
7-
types: [opened, edited, labeled]
7+
types: [labeled]
88
skip-bots: [github-actions, copilot, dependabot]
99

1010
tools:
@@ -47,14 +47,9 @@ or update entries in the community extension catalog.
4747

4848
## Triggering Conditions
4949

50-
This workflow triggers on issue events. **Only process the issue if ALL of these
51-
conditions are met:**
52-
53-
1. The issue has the `extension-submission` label
54-
2. The issue title starts with `[Extension]:`
55-
56-
If the issue does not meet these conditions, add a brief comment explaining that
57-
this workflow only processes extension submission issues, then stop.
50+
This workflow only triggers when the `extension-submission` label is added to an
51+
issue. Before processing, verify that the issue title starts with `[Extension]:`.
52+
If it does not, stop without commenting.
5853

5954
## Step 1 — Read and Parse the Issue
6055

0 commit comments

Comments
 (0)