Skip to content

Conversation

@galz10
Copy link
Collaborator

@galz10 galz10 commented Dec 2, 2025

Summary

Adds a new scheduled GitHub Actions workflow (gemini-scheduled-stale-issue-closer.yml) to automatically tidy up the issue backlog. This workflow identifies and closes old, inactive issues to help maintainers focus on active development and recent bug reports.

Details

The new workflow runs weekly on Sundays and applies the following logic:

Criteria for Closing:

  • Age: Created more than 3 months ago.
  • Inactivity: No updates in the last 10 days.
  • Popularity: Has fewer than 5 reactions.
  • Scope: Processes the oldest 100 open issues to ensure incremental and safe cleanup.

Actions Taken:

  1. Posts a friendly comment encouraging the user to reopen if the issue persists on the latest build.
  2. Closes the issue.

Safety Features:

  • Dry Run Mode: Includes a workflow_dispatch trigger with a dry_run input. This allows maintainers to manually trigger the workflow and verify which issues would be targeted without actually modifying them.

Related Issues

How to Validate

  1. Navigate to the Actions tab in the GitHub repository.
  2. Select the 🔒 Gemini Scheduled Stale Issue Closer workflow from the sidebar.
  3. Click the Run workflow button.
  4. Check the box for "Run in dry-run mode (no changes applied)".
  5. Click Run workflow.
  6. Once completed, open the workflow run logs and verify the "Process Stale Issues" step. It should list issues it would close with [DRY RUN] prefixes.

Pre-Merge Checklist

  • [] Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

   Adds a new GitHub Action `gemini-scheduled-stale-issue-closer.yml` to automatically manage the issue backlog.
   - Runs weekly on Sundays.
   - Closes issues created > 3 months ago with no updates in the last 10 days and < 5 reactions.
   - Adds a friendly comment before closing.
   - Includes a `workflow_dispatch` trigger with a `dry_run` option for safe testing.
   - Currently limits processing to the oldest 100 open issues to ensure safe incremental cleanup.
@galz10 galz10 requested a review from a team as a code owner December 2, 2025 21:24
@gemini-code-assist
Copy link
Contributor

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

@github-actions
Copy link

github-actions bot commented Dec 2, 2025

Size Change: -2 B (0%)

Total Size: 21.5 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 21.5 MB -2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

owner: context.repo.owner,
repo: context.repo.repo,
issue_number: issue.number,
body: "Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.\n\nIt looks like this issue hasn't been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to reopen this issue or create a new one with updated details.\n\nThank you for your contribution!"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since external users are unable to reopen closed issues, can we say:

Suggested change
body: "Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.\n\nIt looks like this issue hasn't been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to reopen this issue or create a new one with updated details.\n\nThank you for your contribution!"
body: "Hello! As part of our effort to keep our backlog manageable and focus on the most active issues, we are tidying up older reports.\n\nIt looks like this issue hasn't been active for a while, so we are closing it for now. However, if you are still experiencing this bug on the latest stable build, please feel free to comment on this issue or create a new one with updated details.\n\nThank you for your contribution!"

@galz10 galz10 requested a review from kklashtorny1 December 3, 2025 01:46
@galz10 galz10 enabled auto-merge December 3, 2025 19:04
@galz10 galz10 added this pull request to the merge queue Dec 3, 2025
Merged via the queue into main with commit 939cb67 Dec 3, 2025
23 checks passed
@galz10 galz10 deleted the galzahavi/add/stale-issue-workflow branch December 3, 2025 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants