-
Notifications
You must be signed in to change notification settings - Fork 8
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
Review and close stale automated-testing issues #832
Comments
I'm ok with either. I'll start with unassigned ones. |
Unassigned issues have either been closed or reassigned for a second look. |
@KatieWoe please skip the repos that I'm responsible for. CT issues are already well-triaged, and it's not a good use of my time to have to reply to every CT issue, reopen, unassign, etc. |
Ah, well... I didn't get to you in time, and you're done. So I guess I'll reply to those issues. |
@KatieWoe @Nancy-Salpepi @stemilymill and I discussed this at QA meeting, and decided this issue has served its purpose and can be closed, thanks! |
We have 112 open issues labeled for automated testing: https://github.com/issues?q=is%3Aissue+user%3Aphetsims+label%3Atype%3Aautomated-testing+is%3Aopen
Can you please look through them and see which can be closed?
UPDATE: Or we can just look through the unassigned ones, and request that the assigned developers each look through their own issues?
The text was updated successfully, but these errors were encountered: