Configure stale workflow: mark stale after 60 days, close after 30 da…

[arbiv]

…ys, upgrade to v10

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow for improved repository maintenance, including upgraded stale action version and adjusted staleness parameters to streamline issue and PR management.

[linear]

CORE-85 add stale to elementary repo

[github-actions]

👋 @arbiv
Thank you for raising your pull request.
Please make sure to add tests and document all user-facing changes.
You can do this by editing the docs files in this pull request.

[coderabbitai]

Walkthrough

Updated the GitHub Actions stale workflow configuration by upgrading the action from version 5 to version 10, reducing the stale threshold from 180 days to 60 days, and introducing a 30-day auto-close period for stale items.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflow Configuration \.github/workflows/stale\.yml	Upgraded actions/stale from v5 to v10; reduced days-before-stale from 180 to 60; added days-before-close: 30 parameter for automatic closure of stale issues and pull requests.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single configuration file with straightforward parameter updates (version bump and numeric value adjustments)
• No logic changes; existing messages and structure preserved

Poem

🐰 A workflow renewed, so spry and so keen,
From v5 to v10, the stalest is seen,
Sixty days now, not one hundred and eighty,
Closing swift after thirty—hopping so weighty!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main changes: configuring stale workflow parameters (60 days to stale, 30 days to close) and upgrading to v10.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch core-85-add-stale-to-elementary-repo

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 6db610e and c3d6be5.

📒 Files selected for processing (1)

• .github/workflows/stale.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: test / test
• GitHub Check: code-quality

🔇 Additional comments (1)

.github/workflows/stale.yml (1)

14-17: Verify the policy change intent and communication.

The upgrade to actions/stale@v10 with days-before-stale: 60 and days-before-close: 30 represents a significant shift in stale handling—marking issues/PRs stale after 60 days instead of 180, then auto-closing 30 days later. This is 3× more aggressive. The default days-before-stale in v10 is 60, so your config aligns with upstream defaults for stale threshold, but the default days-before-close is 7 days, making the 30-day close window custom.

Ensure this policy change is intentional and communicated to the team, as it will impact how long stale issues/PRs remain open before auto-closure.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}