Skip to content

Remove unused gardener investigate workflow and fix the waiting-for-response closer - #2092

Draft
isaacroldan wants to merge 2 commits into
mainfrom
gardener/cleanup-dead-workflows
Draft

isaacroldan wants to merge 2 commits into
mainfrom
gardener/cleanup-dead-workflows

Conversation

@isaacroldan

Copy link
Copy Markdown

What this PR does

Dev Experience gardener cleanup: this removes one workflow that has never run and fixes one that fails every day. Evidence comes from a read-only inventory of the Dev Experience repos' automation taken on 2026-10-27.

Remove gardener-investigate-issue.yml. It has 0 runs since it was added on 2026-04-20, and the devtools-investigate-for-gardener label has never been used in this repo. The investigating-github-issues skill in .claude/skills/ stays because it works locally without the workflow. No docs mention the workflow or the label.

Fix the waiting-for-response closer. close-waiting-for-response-issues.yml has failed every day since 2026-09-25 (latest failure, 2026-10-27, first failure, 2026-09-25, last success, 2026-09-24). Each run stops at "Getting action download info" with Repository access blocked: GitHub has blocked actions-cool/issues-helper itself. gh api repos/actions-cool/issues-helper returns 403 with block reason tos, created 2026-09-24T23:51:05Z.

This PR switches to the setup the remix template has used since 2026-07-13 (file, green run on 2026-10-27). That is actions/stale@1e223db275d687790206a7acac4d1a11bd6fe629 # v10.4.0 with days-before-stale: -1 and days-before-close: -1, so it only closes issues that already carry the "Waiting for Response" label. The label match is case-insensitive.

  • The workflow name, the schedule and the closing message stay the same.
  • The 7-day window stays the same: the old inactive-day value is now days-before-issue-close.
  • actions/stale needs actions: write to save its state cache, so the file now has a permissions block.
  • remove-issue-stale-when-updated: false leaves label removal to remove-labels-on-activity.yml. That workflow is unchanged and still drops the label when someone comments.

No open issue has the label today, so merging this won't close anything right away.

Reviewer's guide to testing

Parsed every workflow in .github/workflows/ with PyYAML (actionlint isn't installed locally). The closer hasn't been run end to end. After merge, workflow_dispatch can trigger it once.

Things to focus on

  1. .github/workflows/close-waiting-for-response-issues.yml: check that the inputs match the remix template's version, apart from the 7-day window and this repo's closing message.

Checklist

  • Update CHANGELOG.md if the changes would impact users: not needed, because this is CI-only and doesn't affect users
  • Update README.md, if appropriate: n/a
  • Update any relevant pages in /docs, if necessary: n/a (no docs reference these workflows)
  • For security fixes, the Disclosure Policy must be followed: n/a

isaacroldan and others added 2 commits October 27, 2026 12:04
The workflow has never run, and the devtools-investigate-for-gardener label has never been used here.

Co-authored-by: Claude Code <claude-code@anthropic.com>
…g-for-response closer

GitHub blocked actions-cool/issues-helper on 2026-09-24, so the workflow has failed every day since 2026-09-25. Use the actions/stale setup the remix template has run since 2026-07-13, keeping the 7-day window and the closing message.

Co-authored-by: Claude Code <claude-code@anthropic.com>
@github-actions github-actions Bot added the devtools-gardener Post the issue or PR to Slack for the gardener label Oct 27, 2026
@isaacroldan isaacroldan changed the title Remove unused Update Template Versions workflow Remove unused gardener investigate workflow and fix the waiting-for-response closer Oct 27, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

devtools-gardener Post the issue or PR to Slack for the gardener

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant