[isaacroldan]

WHY are these changes introduced?

This is part of the gardener cleanup. On 2026-10-30 Isaac decided to remove the gardener Slack notifications. In this repo they posted only devtools-gardener-labelled items and every Dependabot PR to #devtools-gardener-backlog. Each post was a bare linked title, and together they made up most of the channel's noise.

From now on, the Mission Control gardener hub or a Torrent routine will surface new issues and Dependabot PRs.

WHAT is this pull request doing?

Deletes both gardener notification workflows:

• .github/workflows/gardener-notify-event.yml: stashed the event payload when devtools-gardener was applied or when Dependabot opened a PR.
• .github/workflows/gardener-notify-slack.yml: ran on workflow_run, added devtools-gardener to Dependabot PRs and posted a linked title to Slack.

Nothing else in the repo depends only on these two workflows. I grepped for gardener-notify, GARDENER_SLACK, SLACK_GARDENER and devtools-gardener and checked helper scripts, label/config files and docs. This PR doesn't touch the devtools-gardener label, the other workflows or the Mission Control hub. It only changes workflows, so there's no changeset (same as #9022).

After merge, Dependabot PRs will no longer get the devtools-gardener label automatically.

Secrets and variables these workflows used (none are deleted here; removing them is left to the maintainers):

• secrets.SLACK_GARDENER_BOT_TOKEN: still used on main by gardener-investigate-issue.yml (removed in Remove unused gardener workflows and Slack notifications #9022) and maintenance-prs.yml (removed in Remove maintenance-prs workflow and automated task prompts #9047).
• vars.GARDENER_SLACK_CHANNEL_ID: still used on main by gardener-investigate-issue.yml (removed in Remove unused gardener workflows and Slack notifications #9022).

How to manually test your changes?

Nothing to test locally because this only deletes workflows. After merge, labelling an issue or PR devtools-gardener, or Dependabot opening a PR, should no longer run Gardener - Notify Event / Gardener - Notify Slack or post to Slack.

Related

• Remove unused gardener workflows and Slack notifications #9022: earlier gardener cleanup that removes gardener-investigate-issue.yml

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows): CI-only change
• I've considered possible documentation changes: none needed
• I've considered analytics changes to measure impact: none needed
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add: not user-facing, no changeset