Create stale.yml

[arbiv]

Summary by CodeRabbit

• Chores
  • Added automated workflow to manage stale issues and pull requests.
  • Inactive items marked as stale after 60 days of inactivity and closed after 30 additional days, with customized notifications.

[linear]

CORE-85 add stale to oss repo

[coderabbitai]

Walkthrough

A new GitHub Actions workflow is added to automate management of stale issues and pull requests. The workflow runs daily, marks items inactive for 60+ days as stale, and closes them after 30+ additional days, with customized notifications for both issues and PRs.

Changes

Cohort / File(s)	Summary
New GitHub Actions Workflow \.github/workflows/stale\.yml	Added daily-scheduled workflow using actions/stale@v10 to mark and close stale issues and pull requests with configurable inactivity thresholds (60 days to stale, 30 days to close) and custom messages

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify the cron schedule (30 1 * * *) is appropriate for your timezone and workflow frequency
• Confirm the 60-day and 30-day inactivity thresholds align with project maintenance policy
• Review the custom stale and close messages for tone and clarity

Poem

🐰 Hop, hop, the stale issues go,
Marked with care, then fade in snow,
Sixty days of quiet sleep,
Then thirty more, before we sweep!
Tidy repos make rabbits sing! 🥕✨

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 'Create stale.yml' is directly related to the main change in the pull request, which adds a new GitHub Actions workflow file for managing stale issues and PRs.
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-oss-repo

---

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

[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 the elementary repository.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/stale.yml (1)

14-29: Consider adding exemptions for important issue/PR categories.

The workflow will mark and close all stale issues and PRs without exception. For an OSS project, you may want to preserve certain categories indefinitely—such as "good first issue", "documentation", "help wanted", or other community-focused labels.

Consider adding exemptions to preserve important issues:

       - uses: actions/stale@v10
         with:
           days-before-stale: 60
           days-before-close: 30
+          exempt-issue-labels: "good first issue,documentation,help wanted,enhancement"
+          exempt-pr-labels: "documentation,enhancement"
           stale-issue-message: |

Alternatively, if you want to be more selective, you could configure only-labels to only stale/close specific categories rather than exempting.

📜 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 db1ea97 and e7c9b94.

📒 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). (14)

• GitHub Check: test (fusion, bigquery) / test
• GitHub Check: test (latest_official, athena) / test
• GitHub Check: test (latest_official, trino) / test
• GitHub Check: test (latest_official, databricks_catalog) / test
• GitHub Check: test (fusion, redshift) / test
• GitHub Check: test (latest_official, snowflake) / test
• GitHub Check: test (fusion, snowflake) / test
• GitHub Check: test (latest_official, clickhouse) / test
• GitHub Check: test (latest_official, postgres) / test
• GitHub Check: test (fusion, databricks_catalog) / test
• GitHub Check: test (latest_official, dremio) / test
• GitHub Check: test (latest_official, redshift) / test
• GitHub Check: test (latest_pre, postgres) / test
• GitHub Check: test (latest_official, bigquery) / test

🔇 Additional comments (1)

.github/workflows/stale.yml (1)

1-12: Workflow structure and permissions look appropriate.

The workflow is well-structured with clear naming, scheduled trigger, and properly scoped permissions. The daily cron schedule (1:30 UTC) is reasonable for automated maintenance.