mirror of
https://github.com/certbot/certbot.git
synced 2026-05-28 04:34:11 -04:00
b0748b69e7
* Replace probot/stale app with a Github Action This creates a Github Actions workflow which seems to be the supported way of automarking issues as stale. Adds a dry-run flag to test it out. * small fixups * cron typo * disable unnecessary permissions * use friendlier name
42 lines
1.4 KiB
YAML
42 lines
1.4 KiB
YAML
name: Update Stale Issues
|
|
on:
|
|
schedule:
|
|
# Run at midnight every night
|
|
- cron: '24 1 * * *'
|
|
permissions:
|
|
issues: write
|
|
jobs:
|
|
stale:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/stale@v6
|
|
with:
|
|
# REMOVEME: dry run to see if this works
|
|
debug-only: true
|
|
|
|
# Idle number of days before marking issues stale
|
|
days-before-issue-stale: 365
|
|
|
|
# Idle number of days before closing stale issues
|
|
days-before-issue-close: 30
|
|
|
|
# Ignore issues with an assignee
|
|
exempt-all-issue-assignees: true
|
|
|
|
# Label to use when marking as stale
|
|
stale-issue-label: needs-update
|
|
|
|
stale-issue-message: >
|
|
We've made a lot of changes to Certbot since this issue was opened. If you
|
|
still have this issue with an up-to-date version of Certbot, can you please
|
|
add a comment letting us know? This helps us to better see what issues are
|
|
still affecting our users. If there is no activity in the next 30 days, this
|
|
issue will be automatically closed.
|
|
|
|
close-issue-message: >
|
|
This issue has been closed due to lack of activity, but if you think it
|
|
should be reopened, please open a new issue with a link to this one and we'll
|
|
take a look.
|
|
|
|
# Limit the number of actions per hour, from 1-30. Default is 30
|
|
operations-per-run: 1
|