stale.yml 2.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. on:
  2. workflow_dispatch:
  3. schedule:
  4. - cron: '0 10 * * *'
  5. jobs:
  6. prune_stale:
  7. name: Prune Stale
  8. runs-on: ubuntu-latest
  9. steps:
  10. - name: Prune Stale
  11. uses: actions/stale@v4.0.0
  12. with:
  13. days-before-issue-stale: 30
  14. days-before-issue-close: 14
  15. stale-issue-message: >
  16. This issue has been marked as stale due to 30 days of inactivity.
  17. It will be closed in 2 weeks if no further activity occurs. If this
  18. issue is still relevant, please simply write any comment. Even if
  19. closed, you can still revive the issue at any time or discuss it
  20. on the dev@apisix.apache.org list.
  21. Thank you for your contributions.
  22. close-issue-message: >
  23. This issue has been closed due to lack of activity. If you think
  24. that is incorrect, or the issue requires additional review, you
  25. can revive the issue at any time.
  26. days-before-pr-stale: 60
  27. days-before-pr-close: 28
  28. stale-pr-message: >
  29. This pull request has been marked as stale due to 60 days of
  30. inactivity. It will be closed in 4 weeks if no further activity
  31. occurs. If you think that's incorrect or this pull request should
  32. instead be reviewed, please simply write any comment. Even if
  33. closed, you can still revive the PR at any time ordiscuss it on
  34. the dev@apisix.apache.org list.
  35. Thank you for your contributions.
  36. close-pr-message: >
  37. This pull request/issue has been closed due to lack of activity.
  38. If you think that is incorrect, or the pull request requires
  39. review, you can revive the PR at any time.
  40. # Issues with these labels will never be considered stale.
  41. exempt-issue-labels: 'bug,enhancement,good first issue'
  42. stale-issue-label: 'stale'
  43. stale-pr-label: 'stale'
  44. ascending: true