Skip to content

Update stale messages in workflow configuration #12

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

Merged
fcbr merged 1 commit into from
Nov 10, 2025
Merged

Update stale messages in workflow configuration #12

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: '17 14 * * *'

jobs:
stale:

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

steps:
- uses: actions/stale@v5
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}
stale-issue-message: 'Stale issue, will close soon.'
stale-pr-message: 'Stale pull request, will close soon.'
Comment on lines +24 to +25
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

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

The stale messages are not informative or helpful. Users should be given clear guidance on what actions they can take to prevent closure and why the issue/PR is being marked as stale.

Consider more descriptive messages like:

stale-issue-message: 'This issue has been automatically marked as stale due to inactivity. It will be closed in 7 days if no further activity occurs. Please comment if this issue is still relevant.'
stale-pr-message: 'This pull request has been automatically marked as stale due to inactivity. It will be closed in 7 days if no further activity occurs. Please update or comment if this PR is still relevant.'
Suggested change
stale-issue-message: 'Stale issue, will close soon.'
stale-pr-message: 'Stale pull request, will close soon.'
stale-issue-message: 'This issue has been automatically marked as stale due to inactivity. It will be closed in 7 days if no further activity occurs. Please comment if this issue is still relevant.'
stale-pr-message: 'This pull request has been automatically marked as stale due to inactivity. It will be closed in 7 days if no further activity occurs. Please update or comment if this PR is still relevant.'

Copilot uses AI. Check for mistakes.
stale-issue-label: 'no-issue-activity'
stale-pr-label: 'no-pr-activity'
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

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

The stale workflow is missing critical timing parameters. Without specifying days-before-stale and days-before-close, the action will use its default values (60 days before stale, 7 days before close). These defaults may not match your project's needs and should be explicitly configured for clarity and maintainability.

Consider adding these parameters:

days-before-stale: 30
days-before-close: 7
Suggested change
stale-pr-label: 'no-pr-activity'
stale-pr-label: 'no-pr-activity'
days-before-stale: 30
days-before-close: 7

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

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

The workflow lacks important configuration options that would make the stale bot more useful:

  • No exempt-issue-labels or exempt-pr-labels to protect certain issues/PRs from being marked stale
  • No close-issue-message or close-pr-message to inform users when items are actually closed
  • No operations-per-run limit (defaults to 30, which may be too low for repositories with many stale items)

Consider adding these options to provide better control and user experience:

exempt-issue-labels: 'pinned,security,bug'
exempt-pr-labels: 'pinned,work-in-progress'
close-issue-message: 'This issue was automatically closed due to inactivity.'
close-pr-message: 'This pull request was automatically closed due to inactivity.'
Suggested change
stale-pr-label: 'no-pr-activity'
stale-pr-label: 'no-pr-activity'
exempt-issue-labels: 'pinned,security,bug'
exempt-pr-labels: 'pinned,work-in-progress'
close-issue-message: 'This issue was automatically closed due to inactivity.'
close-pr-message: 'This pull request was automatically closed due to inactivity.'
operations-per-run: 100

Copilot uses AI. Check for mistakes.