Adding a github actions to automatically close stale issues/PRs based on CLOUDP-79100 #872
Conversation
| - After 30 days of no activity (no comments or commits on an issue/PR) we automatically tag it as "stale" and add a message: ```This issue/PR has gone 30 days without any activity and meets the project's definition of "stale". This will be auto-closed if there is no new activity over the next 60 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!``` | ||
| - After 60 more days of no activity we automatically close the issue/PR. |
There was a problem hiding this comment.
keeping this consistent with the CLI and go client https://github.com/mongodb/mongodb-atlas-cli/pull/1490/files
|
Let me clean up a few issues before we merge this in. I should be able to do so before the end of the week. Once I do I will approve. @Zuhairahmed is this in line with the policy you wanted to implement. |
There was a problem hiding this comment.
Yes, this is good github issue/PR hygiene and the 30/60 day clock is reasonable for now. we can always adjust cadence in future as needed. thanks again for automating this @andreaangiolillo! just FYI @martinstibbe
|
@andreaangiolillo and @Zuhairahmed just to document it here. We are cleaning up a few last issues and then we'll institute this change. Once we are ready @Zuhairahmed let me know and I'll approve to unblock. |
Description
This is a follow up of #843. This PR adds a cron job (https://github.com/marketplace/actions/close-stale-issues) that scans open issues/PRs and closes them based on the logic decided in CLOUDP-79100: Autoclose stale issues and PRs. We have recently enabled the same cron job for AtlasCLI (#1490) and atlas go client (#318)
Type of change:
Required Checklist:
Further comments