Gardener: require manual label, keep Dependabot auto-label#7362
Merged
byrichardpowell merged 1 commit intomainfrom Apr 21, 2026
Merged
Gardener: require manual label, keep Dependabot auto-label#7362byrichardpowell merged 1 commit intomainfrom
byrichardpowell merged 1 commit intomainfrom
Conversation
The `devtools-gardener` label was applied to every new issue and PR, which posted to Slack on every open — too noisy. Humans now opt in by applying the label manually. Dependabot PRs are still auto-labeled so they continue to surface in the gardener flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the Gardener Slack notification workflows so that Slack posting is gated by a manually applied devtools-gardener label for human-created issues/PRs, while keeping Dependabot PRs automatically labeled (and posted) to ensure dependency updates remain visible.
Changes:
- Stop capturing
issues: openedevents so human-opened issues no longer auto-post to Slack. - Gate
pull_request_target: openedcapture to Dependabot PRs only; keeplabeledcapture for manualdevtools-gardener. - Scope downstream auto-labeling to only Dependabot-opened PRs in the
workflow_runworkflow.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/gardener-notify-event.yml | Adjusts event capture triggers/conditions to only pass through manual devtools-gardener labels and Dependabot-opened PRs. |
| .github/workflows/gardener-notify-slack.yml | Limits auto-labeling to Dependabot-opened PRs while continuing to post Slack summaries for captured events. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ryancbahan
approved these changes
Apr 21, 2026
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.
Summary
Changes the gardener Slack notifier so that the
devtools-gardenerlabel (which gates Slack posting) must be applied manually for human-opened issues and PRs. Dependabot-opened PRs are still auto-labeled.Why
The previous flow applied
devtools-gardenerto every newly opened issue and PR. This repo gets a lot of PR's, many of which don't need to be reviewed by this team. So it was too noisy.Dependabot PRs are kept auto-labeled because we always want dependency updates to surface for triage, and there's no human to apply the label.
Behavior matrix
devtools-gardenerHow it works
gardener-notify-event.yml(capture):openedfromissues:types — issues now only capture onlabeled.openedonpull_request_target:but the jobifonly admits it when the opener isdependabot[bot].labeledevents still pass through when the label isdevtools-gardener.gardener-notify-slack.yml(downstream workflow_run):action == opened && login == dependabot[bot]) instead of everyopenedevent.GITHUB_TOKENdon't trigger anotherlabeledrun (GitHub's loop-prevention).The two-workflow pattern is still needed: Dependabot-triggered workflows have read-only
GITHUB_TOKENand no Actions secret access, so labeling and Slack posting happen in theworkflow_runfollow-up which runs in the default-branch context.