Skip to content

add gha to label and close stale pull requests #290

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kristinmerbach wants to merge 1 commit into
base: trunk
Choose a base branch
from
Open

add gha to label and close stale pull requests #290

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions .github/workflows/stale.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# This workflow warns and then closes issues and PRs that have had no activity for a specified amount of time.
#
# You can adjust the behavior by modifying this file.
# For more information, see:
# https://github.com/actions/stale
name: Mark stale issues and pull requests

on:
schedule:
- cron: "06 6 * * *"

jobs:
stale:
runs-on: ubuntu-latest
permissions:
issues: write
pull-requests: write

steps:
- uses: actions/stale@v5
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Oct 21, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Update actions/stale to a compatible version.

The static analysis tool (actionlint) flags that actions/stale@v5 is incompatible with the current GitHub Actions runner. This will cause the workflow to fail at runtime.

Please update the action to a more recent version:

-      - uses: actions/stale@v5
+      - uses: actions/stale@v10

Note: The version number is a suggestion; please verify the latest stable version of the stale action available.

🌐 Web query:

What is the latest stable version of the actions/stale GitHub Action?

💡 Result:

The latest stable version is v10.1.0. [1]

Sources
[1] actions/stale package page on GitHub Packages (shows 10.1.0 as Latest).

Update actions/stale to v10.1.0.

The latest stable version of actions/stale is v10.1.0. The current version v5 in line 20 is incompatible with the current GitHub Actions runner and will cause the workflow to fail at runtime.

-      - uses: actions/stale@v5
+      - uses: actions/stale@v10.1.0
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- uses: actions/stale@v5
- uses: actions/stale@v10.1.0
🧰 Tools
🪛 actionlint (1.7.8)

20-20: the runner of "actions/stale@v5" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

🤖 Prompt for AI Agents 
In .github/workflows/stale.yml around line 20, the workflow references
actions/stale@v5 which is incompatible with the current GitHub Actions runner;
update the action to actions/stale@v10.1.0 by replacing the uses value
accordingly and verify any required inputs or minor syntax changes for v10.1.0
(e.g., ensure required tokens or parameters are present) so the workflow runs
without runtime failures.

with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: "Stale issue message"
stale-pr-message: "Stale pull request message"
Comment on lines +23 to +24
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot Oct 21, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Replace placeholder messages with actionable, descriptive text.

The stale messages are generic placeholders that don't provide useful information to contributors. Users should understand why their item is marked as stale and what actions they can take to keep it active.

Consider updating the messages with more context:

-          stale-issue-message: "Stale issue message"
-          stale-pr-message: "Stale pull request message"
+          stale-issue-message: "This issue has been inactive for 30 days. Please add a comment or update the issue if it is still relevant, otherwise it will be closed in 7 days."
+          stale-pr-message: "This pull request has been inactive for 30 days. Please add a comment or make updates if you're still working on it, otherwise it will be closed in 7 days."

Customize these messages as appropriate for your repository's workflow and community guidelines.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
stale-issue-message: "Stale issue message"
stale-pr-message: "Stale pull request message"
stale-issue-message: "This issue has been inactive for 30 days. Please add a comment or update the issue if it is still relevant, otherwise it will be closed in 7 days."
stale-pr-message: "This pull request has been inactive for 30 days. Please add a comment or make updates if you're still working on it, otherwise it will be closed in 7 days."
🤖 Prompt for AI Agents 
In .github/workflows/stale.yml around lines 23 to 24, the stale-issue-message
and stale-pr-message are generic placeholders; replace them with actionable,
descriptive messages that explain why the issue/PR is being marked stale, the
timeframe that triggered it, and clear instructions for maintainers/contributors
on how to reactivate it (e.g., provide a status update, reply, or reopen with
new information); ensure messages are concise, reference the inactivity period,
and include a link or reference to contribution guidelines if applicable.

stale-issue-label: "no-issue-activity"
stale-pr-label: "no-pr-activity"
days-before-stale: 30
Loading