Closing GH Issues #5971
Closing GH Issues #5971
Conversation
|
I plan to delete the include once I am done closing issues. |
|
#sign-off |
|
@IngridAtMicrosoft: I'm sorry - only the author of this article, @, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias. |
|
Closes #2170 |
|
I didn't get a single comment on my issue which has now been closed by this Feels a bit off, thought I was being helpful |
|
I get that quite a few of the closed issues are actually issues that should never have been opened on this repo, that some are already fixed and forgotten to close and that some might just be no longer relevant. BUT: There are also many that are absolutely valid, still relevant and not fixed. E.g. #1177, #2157, #605, #753, #1483, .... (and more, I just randomly checked a few) I don't think microsoft should just close all old issues without checking whether they are solved. Especially not without an explanation and without ability to reopen ones own issue. |
That's what open issues are for! Just reopen them all. IMHO it's much better to have open issues that could have been closed, than to have closed issues that should have stayed open. |
I realize that I am an FTE and this isn't the usual route for making PRs. However, this is to test the closing of stale issues for the repo.
This PR closes #2112.