Skip to content

add github action to automatically handle stale user support issues #4683

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
merged 3 commits into from
Aug 31, 2024
Merged

add github action to automatically handle stale user support issues #4683

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a89d576
add github action to automatically handle stale user support issues
mcmonkey4eva Aug 29, 2024
dd4c71a
improve stale message
mcmonkey4eva Aug 30, 2024
ff99ff9
remove token part
mcmonkey4eva Aug 31, 2024
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
23 changes: 23 additions & 0 deletions .github/workflows/stale-issues.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
name: 'Close stale issues'
on:
schedule:
# Run daily at 430 am PT
- cron: '30 11 * * *'
permissions:
issues: write

jobs:
stale:
runs-on: ubuntu-latest
steps:
- uses: actions/stale@v9
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Copy link
Owner

Choose a reason for hiding this comment

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

why do you need this here?

Copy link
Contributor Author

@mcmonkey4eva mcmonkey4eva Aug 30, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

the action interacts with & controls repo issues - labelling, commenting, closing. The official actions/stale doc examples don't actually work (???) but commenters in the repo say you need github_token and/or permissions: key to work (and when I tested adding them, it started working)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Update, tested and confirmed that

permissions:
  issues: write

is needed but the token is not, so I've remove the token part

with:
stale-issue-message: 'This issue is being marked stale because it has not had any activity for 30 days. Reply below within 7 days if it should be left open.'
Copy link
Owner

Choose a reason for hiding this comment

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

How about a "reply if your issue still isn't solved"?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

tweaked phrasing:
This issue is being marked stale because it has not had any activity for 30 days. Reply below within 7 days if your issue still isn't solved, and it will be left open. Otherwise, the issue will be closed automatically.

days-before-stale: 30
days-before-close: 7
stale-issue-label: 'Stale'
only-labels: 'User Support'
exempt-all-assignees: true
exempt-all-milestones: true