You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 18, 2021. It is now read-only.
Thanks for the suggestion. It's only possible to edit/clear the issue content currently. However I've added a +1 to this suggestion on our internal Feature Request List.
Likely GitHub does not implement this because then the asker would be able to remove useful answers from other people (but as usual GitHub is very secretive and does not give us rationale). There are two possibilities to reduce that concern:
SO 93 upvotes: http://stackoverflow.com/questions/3081521/removing-github-issues . Seems impossible today. As pointed by CommuSoft there, might be illegal in Europe =)
E.g.: I was doing two things at the same time and created an issue on the bad repo: markdownlint/markdownlint#46
https://github.com/jdennes replied:
Likely GitHub does not implement this because then the asker would be able to remove useful answers from other people (but as usual GitHub is very secretive and does not give us rationale). There are two possibilities to reduce that concern:
allow project admins to do it only as proposed on GitLab: http://feedback.gitlab.com/forums/176466-general/suggestions/6584418-remove-issues-and-milestones
This should definitely be allowed, considering that the owner can already destroy the entire repo in one go...
allow OP to remove it if there are no answers somewhat like Stack Overflow: http://meta.stackexchange.com/questions/5221/how-does-deleting-work-what-can-cause-a-post-to-be-deleted-and-what-does-that
I don't see why not, and would solve many cases.