Implementing GH Actions to close Stale Issues

This commit is contained in:
Alejandro Chavarria 2022-05-06 09:33:45 -06:00
parent 5cbd400756
commit 05bbc3e947
1 changed files with 4 additions and 5 deletions

View File

@ -21,9 +21,9 @@ jobs:
# Implementing ancient issue closure only at the moment.
ancient-issue-message: 'This is a very old issue that is probably not getting as much
attention as it deserves.
We encourage you to check if this is still an issue in
We encourage you to check if this is still an issue after
the latest release and if you find that this is still a problem, please feel free
to provide a comment or open a new issue.'
to open a new issue and make a reference to this one.'
#stale-issue-message: 'It looks like this issue has not been active for more than five days.
#In the absence of more information, we will be closing this issue soon.
#If you find that this is still a problem, please add a comment to prevent automatic closure, or
@ -40,9 +40,8 @@ jobs:
# Issue timing. Setting ancient issues to 6 months and stale to 1 month with no activity.
# Issue will automatically close after 5 days of being marked as stale.
# For Dry-run purposes, closing issues after 1 day.
#days-before-stale: 30
days-before-close: 1
days-before-close: 5
days-before-ancient: 180
# If you don't want to mark an issue as being ancient based on a
@ -55,4 +54,4 @@ jobs:
repo-token: ${{ secrets.GITHUB_TOKEN }}
loglevel: DEBUG
# Set dry-run to true to not perform label or close actions.
dry-run: true
#dry-run: true