-
Notifications
You must be signed in to change notification settings - Fork 881
Issue Cleanup Round #1 #3276
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
Comments
I agree with closing all! |
I think #909, which is currently on the proposed August roadmap, depends on #44. Depending on the implementation, it might also depend on #1391, #1392, #1393, and/or #1605. Many of these sound like issues that we've said we do plan to implement at some point, even though the issue descriptions might be out of date. Do we plan to reopen them when we eventually get around to them? |
@dwahler yes! closing does not mean its forever closed. any of them can always be reopened. |
@dwahler after reading through those tickets it seemed to me the plan and details were out of date. Closing these tickets in no way implies that work won't be planned or worked on, but that these tickets being open and existing are not helping us right now. |
@spikecurtis @dwahler I reopened the ones I think are relevant to your work, sorry for misunderstanding and jumping the gun on that. |
@f0ssel No problem at all, and thanks for doing this cleanup! |
We have an overwhelming amount of issues that go stale and are better off being remade when they come back up in priority. In our retro today this was brought up again. I'm trying to go through old issues that have the following problems:
Remembering that all issues can easily be reopened at a later date, I would like to close the following:
/workspaces
to allow for filtered and paginated queryingΒ #1477make bin
is not sufficient when testing changesΒ #1547coder reset-password
should be nested undercoder users
Β #1631The text was updated successfully, but these errors were encountered: