ongdisheng commented on issue #681: URL: https://github.com/apache/fesod/issues/681#issuecomment-3507629193
Hi @delei, I'd like to help implement this. The approach makes sense and gives reporters enough time to respond while keeping the issue tracker manageable. ## Implementation I think we can use the [actions/stale](https://github.com/actions/stale) for this. It handles Phase 2 and Phase 3 automatically in which the workflow runs daily and only processes issues that maintainers have already labeled `waiting for feedback` in Phase 1. ## How it works Maintainers manually add the `waiting for feedback` label when they need more info from reporters. After 30 days without activity, the bot adds a `stale` label and warns that the issue will close in 7 days. If there's still no response after those 7 days, it closes the issue automatically. ## Sample workflow Here's what the workflow file would look like: ```yml name: Close Stale Issues on: schedule: - cron: '0 0 * * *' workflow_dispatch: permissions: issues: write jobs: stale: runs-on: ubuntu-latest steps: - uses: actions/stale@v10 with: only-labels: 'waiting for feedback' days-before-stale: 30 days-before-close: 7 stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.' close-issue-message: 'This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.' stale-issue-label: 'stale' days-before-pr-stale: -1 days-before-pr-close: -1 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
