Skip to content

Add stale issue/PR workflow#302

Merged
anasstahr merged 2 commits into
mainfrom
add-stale-workflow
Jun 3, 2026
Merged

Add stale issue/PR workflow#302
anasstahr merged 2 commits into
mainfrom
add-stale-workflow

Conversation

@anasstahr

Copy link
Copy Markdown
Contributor

Summary

Changes

Add a GitHub Actions workflow to automatically mark and close stale issues and PRs. This mirrors the configuration already in use at aws/agent-toolkit-for-aws:

  • Issues are marked stale after 60 days of inactivity, then closed after 14 more days
  • PRs are marked stale after 14 days of inactivity, then closed after 7 more days
  • Uses actions/stale@v10.3.0 with a pinned commit hash

User experience

Before: Issues and PRs remain open indefinitely regardless of activity.

After: Inactive issues/PRs receive a stale warning comment, then auto-close if no further activity occurs. Any new activity resets the timer.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

  • I have reviewed the contributing guidelines
  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented

Is this a breaking change? (Y/N)

  • Yes
  • No

Please add details about how this change was tested.

  • Did integration tests succeed?
  • If the feature is a new use case, is it necessary to add a new integration test case?

Validated workflow syntax. No integration test needed — this is a scheduled GitHub Actions workflow with no impact on application code.

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Automatically mark issues stale after 60 days and close after 14 more.
PRs are marked stale after 14 days and closed after 7 more.
Mirrors the configuration from aws/agent-toolkit-for-aws.
@anasstahr anasstahr requested a review from a team as a code owner June 3, 2026 13:58
@anasstahr anasstahr requested review from arnewouters and vtols June 3, 2026 13:58

@arnewouters arnewouters left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we skip feature requests being marked stale?

Issues labeled feature-request or enhancement will not be
marked stale or auto-closed.
@anasstahr anasstahr added this pull request to the merge queue Jun 3, 2026
Merged via the queue into main with commit 6bcc27c Jun 3, 2026
8 checks passed
@anasstahr anasstahr deleted the add-stale-workflow branch June 3, 2026 17:25
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.

2 participants