fix: restrict community submission workflows to labeled event only#2741
Merged
Merged
Conversation
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 github#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
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.
Problem
Both
add-community-presetandadd-community-extensionworkflows triggered onissues: [opened, edited, labeled]events. This caused them to fire on every new issue and post noisy bot comments explaining the issue wasn't a submission.Fix
[opened, edited, labeled]to[labeled]only — the workflow now only fires when a maintainer adds a labelThis means a maintainer must apply the
preset-submissionorextension-submissionlabel for the respective workflow to run, which is the intended gate.