-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce automation to help GC GitHub issues #1274
Comments
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. |
We now have automation in place to label stale issues and PRs, and I think we've agreed that's about as far as we want to go for now. Anything more to do here, or OK to close this issue @tsandall ? |
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. |
Closing for now. Let’s create a new one if we want specific improvements later. |
As the project gets older, we're going to continue to accumulate open issues. While many of the issues in the current backlog are valuable, it would be nice to have period reminders to clean up stale and out-of-date issues.
One option would be to run prow on the OPA repo to manage issue lifecycle.
I'd like to avoid relying in prow for other CI/CD functions at this point, but using it for issue labeling seems reasonable.
The text was updated successfully, but these errors were encountered: