Skip to content

chore: clarify stale issue and PR guidance #4772

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
mnriem merged 2 commits into from
Sep 28, 2026
Merged

chore: clarify stale issue and PR guidance #4772

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
961e7a9
chore: clarify stale closure guidance
mnriem Sep 28, 2026
66b5e96
fix: make stale reopening guidance actionable
mnriem Sep 28, 2026
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
28 changes: 24 additions & 4 deletions .github/workflows/stale.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,13 +22,33 @@ jobs:
days-before-close: 30

# Stale issue settings
stale-issue-message: 'This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed in 30 days if no further activity occurs.'
close-issue-message: 'This issue has been automatically closed due to inactivity (90 days total). If you believe this issue is still relevant, please reopen it or create a new issue.'
stale-issue-message: >-
This issue has been automatically marked as stale because it has had no activity for 60 days.
It will be closed in 30 days unless there is a substantive update. If the problem still applies,
please provide updated context such as whether it is still reproducible, the affected version or
environment, its current impact, and any new reproduction details. A comment that only states that
the issue is "still relevant" does not give maintainers enough information to reconsider it.
close-issue-message: >-
This issue has been automatically closed after 90 days without activity. To request reconsideration,
please provide updated reproduction details, the currently affected version or environment, and the
present impact. Ask a maintainer to reopen this issue if it is fundamentally the same problem. If the
scope or reproduction has materially changed, create a new issue, link this one, and explain what has
changed.
stale-issue-label: 'stale'

# Stale PR settings
stale-pr-message: 'This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed in 30 days if no further activity occurs.'
close-pr-message: 'This pull request has been automatically closed due to inactivity (90 days total). If you believe this PR is still relevant, please reopen it or create a new PR.'
stale-pr-message: >-
This pull request has been automatically marked as stale because it has had no activity for 60 days.
It will be closed in 30 days unless there is a substantive update. If you intend to continue, please
describe the current status, address or acknowledge outstanding feedback, and confirm whether the
branch can be updated and the change remains ready for review. A comment that only states that the
pull request is "still relevant" does not provide enough context for maintainers.
close-pr-message: >-
This pull request has been automatically closed after 90 days without activity. To request
reconsideration, please explain why the change is still needed, confirm that the implementation is
current and ready for review, and address any outstanding feedback or conflicts. Ask a maintainer to
reopen this pull request if the existing branch and approach remain valid. Otherwise, create a new pull
request, link this one, and explain what has changed.
stale-pr-label: 'stale'

# Exempt issues and PRs with these labels from being marked as stale
Expand Down
Loading