add workflow to label issues as stale

[rahulait]

Description

This PR adds the workflow which runs periodically and labels issues as stale if there is no activity for a certain period.

Motivation

To keep all our repos in sync on how we handle issues, we are adding this worklow to this repo as well.

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 📝 Documentation update
• 🔧 Refactoring (no functional changes)
• 🧪 Test improvements
• 🔨 Build/CI changes

Changes Made

Testing

• Unit tests added/updated
• E2E tests added/updated
• Manual testing performed

Test Commands Run

# Commands used to test the changes
make test
make lint

Checklist

• My code follows the project's coding conventions
• I have performed a self-review of my code
• I have commented my code where necessary
• I have updated the documentation (if applicable)
• My changes generate no new warnings
• I have added tests that prove my fix/feature works
• New and existing tests pass locally
• I have signed off my commits (git commit -s)

Additional Notes

[Copilot]

Pull request overview

Adds a scheduled GitHub Actions workflow to automatically mark inactive issues as stale and eventually close them, helping keep issue hygiene consistent across repositories.

Changes:

• Introduces a new scheduled workflow (stale.yaml) using actions/stale@v10.
• Configures stale/close timings and messages for inactive issues.
• Defines job-level permissions for the stale automation.

[Copilot]

The job requests actions: write, but actions/stale only needs to read/update issues (and optionally pull requests). Granting actions: write is broader than necessary; please remove it to follow least-privilege permissions.

Suggested change

actions: write

[rahulait]

This is intentional as its required to clean stale cache. See actions/stale#1248

[Copilot]

actions/stale processes pull requests by default. This workflow only grants issues: write, so runs may fail when the action tries to label/close PRs. If the intent is issues-only, set only-issues: true (or disable PR handling); otherwise add pull-requests: write permission and configure the PR-specific settings/messages.

[rahulait]

This is incorrect suggestion. There is no only-issues: true option and this workflow is not touching PRs, its only labeling/closing issues here as configured. See https://github.com/actions/stale?tab=readme-ov-file#all-options

If someone wants to label PRs as well in future, those permissions should be set then.

[coveralls]

Pull Request Test Coverage Report for Build 22634518209

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 48.275%

---

Totals
Change from base Build 22623448927:	0.0%
Covered Lines:	2617
Relevant Lines:	5421

---

💛 - Coveralls

[ArangoGutierrez]

Thanks for the PR, please address copilot comments before we can move on

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[rahulait]

Thanks for the PR, please address copilot comments before we can move on

I've addressed all the issues reported by copilot. PTAL

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.