How to completely remove an issue from GitHub?











up vote
376
down vote

favorite
35












Is it possible to completely remove an issue from the GitHub issue tracker?






github privacy issue-tracking







share|improve this question




















  • 25




    An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
    – Willem Van Onsem
    Aug 12 '14 at 21:04






  • 2




    @CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    Aug 15 '14 at 9:10








  • 1




    @CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
    – Marek Lewandowski
    Apr 28 '15 at 20:23






  • 1




    @MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
    – Willem Van Onsem
    Apr 28 '15 at 21:12






  • 2




    @MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    May 31 '15 at 20:40















up vote
376
down vote

favorite
35












Is it possible to completely remove an issue from the GitHub issue tracker?






github privacy issue-tracking







share|improve this question




















  • 25




    An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
    – Willem Van Onsem
    Aug 12 '14 at 21:04






  • 2




    @CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    Aug 15 '14 at 9:10








  • 1




    @CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
    – Marek Lewandowski
    Apr 28 '15 at 20:23






  • 1




    @MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
    – Willem Van Onsem
    Apr 28 '15 at 21:12






  • 2




    @MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    May 31 '15 at 20:40













up vote
376
down vote

favorite
35









up vote
376
down vote

favorite
35






35





Is it possible to completely remove an issue from the GitHub issue tracker?






github privacy issue-tracking







share|improve this question















Is it possible to completely remove an issue from the GitHub issue tracker?






github privacy issue-tracking




github privacy issue-tracking






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 17 '15 at 22:52









kenorb

63k27377386




63k27377386










asked Jun 21 '10 at 0:32









YGL

2,99021619




2,99021619








  • 25




    An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
    – Willem Van Onsem
    Aug 12 '14 at 21:04






  • 2




    @CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    Aug 15 '14 at 9:10








  • 1




    @CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
    – Marek Lewandowski
    Apr 28 '15 at 20:23






  • 1




    @MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
    – Willem Van Onsem
    Apr 28 '15 at 21:12






  • 2




    @MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    May 31 '15 at 20:40














  • 25




    An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
    – Willem Van Onsem
    Aug 12 '14 at 21:04






  • 2




    @CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    Aug 15 '14 at 9:10








  • 1




    @CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
    – Marek Lewandowski
    Apr 28 '15 at 20:23






  • 1




    @MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
    – Willem Van Onsem
    Apr 28 '15 at 21:12






  • 2




    @MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
    – Ciro Santilli 新疆改造中心 六四事件 法轮功
    May 31 '15 at 20:40








25




25




An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
– Willem Van Onsem
Aug 12 '14 at 21:04




An interesting side-question: How is this answer legally consistent? I don't know about the U.S. but in Europe one has author-rights (they go beyond copyright) that says one has control about how/if something is published. This means one can decide to withdraw a publication. This right can't even be transmitted to a third party (it's a moral right).
– Willem Van Onsem
Aug 12 '14 at 21:04




2




2




@CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Aug 15 '14 at 9:10






@CommuSoft Nice consideration. Maybe suing them through the Right to be forgotten is the best option for Europeans today.
– Ciro Santilli 新疆改造中心 六四事件 法轮功
Aug 15 '14 at 9:10






1




1




@CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
– Marek Lewandowski
Apr 28 '15 at 20:23




@CommuSoft Technically, you're able to edit the title / msg so I belive it would be easily defendable for GH. : )
– Marek Lewandowski
Apr 28 '15 at 20:23




1




1




@MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
– Willem Van Onsem
Apr 28 '15 at 21:12




@MarekLewandowski: that's indeed a possibility given Github doesn't keep track of the changes (or you can at least remove history). I know Google faces the same problem with cached versions of webpages. In rare occasions you can for instance ask Google to remove certain pages/history for instance if your name has been cleared in court, you can ask to remove links to articles stating you were suspected of some crime.
– Willem Van Onsem
Apr 28 '15 at 21:12




2




2




@MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
– Ciro Santilli 新疆改造中心 六四事件 法轮功
May 31 '15 at 20:40




@MarekLewandowski true for issue body, but not title, which shows undeletable "changed the title to" comments.
– Ciro Santilli 新疆改造中心 六四事件 法轮功
May 31 '15 at 20:40












9 Answers
9






active

oldest

votes

















up vote
16
down vote



accepted










Update Nov 2018: You now can delete your issues!

See "Github - remove issues entered in error"



Issue deletion




At May 2018, original answer:



Three 8 years later, and closing issues remains the answer (still no deletion possible).

See "The Ghost of Issues Past", where GitHub advise to check and close:




  • issues opened over a year ago state:open created:<2013-01-01

  • the ones I'm involved with involves:twp state:open created:<2013-01-01

  • and those not updated in the last year involves:twp state:open updated:<2013-01-01






share|improve this answer



















  • 25




    This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
    – Alexandre Martins
    Mar 11 '14 at 11:56






  • 7




    @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
    – Jonathan
    Jul 7 '14 at 11:49








  • 41




    Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
    – Volte
    Aug 3 '14 at 6:11






  • 2




    @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
    – FichteFoll
    Nov 27 '14 at 19:08








  • 2




    @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
    – Pacerier
    Jun 4 '15 at 6:46


















up vote
219
down vote













No, the github API only allows you to open/close/reopen issues. Here's the Issues API docs.






share|improve this answer



















  • 1




    Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
    – jww
    Jun 20 '16 at 4:42






  • 19




    Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
    – Sliq
    Apr 15 '17 at 13:17








  • 4




    Or you can use gitlab.com
    – frmdstryr
    Oct 19 '17 at 14:43










  • Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
    – Mateusz Konieczny
    Jul 28 at 16:11










  • This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
    – StingyJack
    Aug 23 at 12:01


















up vote
62
down vote













You can edit an existing issue (let's say if it's a duplicate) and you can change the title, description and target milestone to be something completely different. That's as close as you can get to removing the ticket, AFIK.






share|improve this answer

















  • 4




    Note that it's not possible to edit the title of an issue posted by another user.
    – ocodo
    Dec 1 '12 at 23:41










  • @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
    – Sourabh
    Apr 23 '14 at 13:39








  • 5




    This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
    – Daniel Imms
    Oct 9 '14 at 16:58


















up vote
31
down vote













For posterity: Deleting issues would be a bad thing, since in general they can be targets of associations on github.



But if you are willing to sacrifice the collaboration info, here is a "whack it with a sledgehammer" approach:




  1. Clone your original repo.

  2. Copy your issues via the Issues API.

  3. Delete the original repo; alternatively, chose a new name for your new repo.

  4. Re-create a new repo based on your clone.

  5. Re-create the issues you want to keep via the Issues API.


I imagine this could potentially lose a lot of other linking information as well such as forks, pull requests, etc.






share|improve this answer

















  • 6




    Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
    – Joseph Wright
    May 16 '13 at 5:58






  • 37




    LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
    – Sandeep Raju Prabhakar
    Jul 1 '13 at 21:20






  • 12




    This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
    – Volte
    Aug 3 '14 at 6:14






  • 3




    I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
    – jerseyboy
    Aug 4 '14 at 12:23






  • 1




    What is a "target of association" (in your first paragraph)? (English is not my native language)
    – KajMagnus
    Aug 15 '15 at 7:34




















up vote
28
down vote













Public feature request



I wrote to GitHub in 2014-08 and https://github.com/jdennes replied by email:




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.




confirming it was not possible.



Best workaround so far





  • set the title to something that will never conflict with any search, e.g. a single dot ..



    This may not hide the history of your blunder entirely because of the automatic undeletable "changed the title to" comments.



  • make the body empty



GitHub staff has the power



If something is a security issue, contact GitHub staff, they usually reply quickly, and are able to remove issues for good as can be seen at: http://archive.is/OfjVt which has issue 1 and 3 but no 2.






share|improve this answer






























    up vote
    9
    down vote













    You can delete the entire repo if it's really important.






    share|improve this answer

















    • 3




      +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
      – Dan Lugg
      May 4 '17 at 0:35


















    up vote
    0
    down vote













    You could by just asking to github to ban the user that created the issue 😁



    Source: https://github.com/isaacs/github/issues/253#issuecomment-290944938






    share|improve this answer






























      up vote
      0
      down vote













      Users are unable to do this, including repository owner.



      But issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.






      share|improve this answer




























        up vote
        0
        down vote













        Still impossible. Another workaround to the ones suggested in the other answers is to label the issue as "deleted" (or any other label you might fancy better), to be able to filter them out if you use the github API to retrieve them. Obviously you should use that specific label only for this purpose, setting the label when you close the issue.






        share|improve this answer





















        • Now it is possible
          – Radium Zheng
          Nov 8 at 22:13










        • yes it is at last
          – Mark Kaplun
          Nov 9 at 5:41










        protected by Josh Crozier Nov 27 '17 at 0:53



        Thank you for your interest in this question.
        Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



        Would you like to answer one of these unanswered questions instead?














        9 Answers
        9






        active

        oldest

        votes








        9 Answers
        9






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes








        up vote
        16
        down vote



        accepted










        Update Nov 2018: You now can delete your issues!

        See "Github - remove issues entered in error"



        Issue deletion




        At May 2018, original answer:



        Three 8 years later, and closing issues remains the answer (still no deletion possible).

        See "The Ghost of Issues Past", where GitHub advise to check and close:




        • issues opened over a year ago state:open created:<2013-01-01

        • the ones I'm involved with involves:twp state:open created:<2013-01-01

        • and those not updated in the last year involves:twp state:open updated:<2013-01-01






        share|improve this answer



















        • 25




          This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
          – Alexandre Martins
          Mar 11 '14 at 11:56






        • 7




          @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
          – Jonathan
          Jul 7 '14 at 11:49








        • 41




          Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
          – Volte
          Aug 3 '14 at 6:11






        • 2




          @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
          – FichteFoll
          Nov 27 '14 at 19:08








        • 2




          @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
          – Pacerier
          Jun 4 '15 at 6:46















        up vote
        16
        down vote



        accepted










        Update Nov 2018: You now can delete your issues!

        See "Github - remove issues entered in error"



        Issue deletion




        At May 2018, original answer:



        Three 8 years later, and closing issues remains the answer (still no deletion possible).

        See "The Ghost of Issues Past", where GitHub advise to check and close:




        • issues opened over a year ago state:open created:<2013-01-01

        • the ones I'm involved with involves:twp state:open created:<2013-01-01

        • and those not updated in the last year involves:twp state:open updated:<2013-01-01






        share|improve this answer



















        • 25




          This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
          – Alexandre Martins
          Mar 11 '14 at 11:56






        • 7




          @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
          – Jonathan
          Jul 7 '14 at 11:49








        • 41




          Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
          – Volte
          Aug 3 '14 at 6:11






        • 2




          @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
          – FichteFoll
          Nov 27 '14 at 19:08








        • 2




          @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
          – Pacerier
          Jun 4 '15 at 6:46













        up vote
        16
        down vote



        accepted







        up vote
        16
        down vote



        accepted






        Update Nov 2018: You now can delete your issues!

        See "Github - remove issues entered in error"



        Issue deletion




        At May 2018, original answer:



        Three 8 years later, and closing issues remains the answer (still no deletion possible).

        See "The Ghost of Issues Past", where GitHub advise to check and close:




        • issues opened over a year ago state:open created:<2013-01-01

        • the ones I'm involved with involves:twp state:open created:<2013-01-01

        • and those not updated in the last year involves:twp state:open updated:<2013-01-01






        share|improve this answer














        Update Nov 2018: You now can delete your issues!

        See "Github - remove issues entered in error"



        Issue deletion




        At May 2018, original answer:



        Three 8 years later, and closing issues remains the answer (still no deletion possible).

        See "The Ghost of Issues Past", where GitHub advise to check and close:




        • issues opened over a year ago state:open created:<2013-01-01

        • the ones I'm involved with involves:twp state:open created:<2013-01-01

        • and those not updated in the last year involves:twp state:open updated:<2013-01-01







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 7 at 18:24

























        answered Dec 18 '13 at 8:17









        VonC

        822k28425833101




        822k28425833101








        • 25




          This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
          – Alexandre Martins
          Mar 11 '14 at 11:56






        • 7




          @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
          – Jonathan
          Jul 7 '14 at 11:49








        • 41




          Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
          – Volte
          Aug 3 '14 at 6:11






        • 2




          @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
          – FichteFoll
          Nov 27 '14 at 19:08








        • 2




          @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
          – Pacerier
          Jun 4 '15 at 6:46














        • 25




          This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
          – Alexandre Martins
          Mar 11 '14 at 11:56






        • 7




          @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
          – Jonathan
          Jul 7 '14 at 11:49








        • 41




          Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
          – Volte
          Aug 3 '14 at 6:11






        • 2




          @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
          – FichteFoll
          Nov 27 '14 at 19:08








        • 2




          @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
          – Pacerier
          Jun 4 '15 at 6:46








        25




        25




        This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
        – Alexandre Martins
        Mar 11 '14 at 11:56




        This is a bummer. A week ago, I accidentally submitted an issue to the wrong project. And now it is forever polluting that projects tracker when it clearly should not be there.
        – Alexandre Martins
        Mar 11 '14 at 11:56




        7




        7




        @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
        – Jonathan
        Jul 7 '14 at 11:49






        @AlexandreMartins I've just done the same thing. Seems absolutely STUPID that there isn't a way to delete issues that genuinely make no sense to be there. POWER to the USER/OWNER damn it!
        – Jonathan
        Jul 7 '14 at 11:49






        41




        41




        Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
        – Volte
        Aug 3 '14 at 6:11




        Had the exact same thing happen via Zappier when I joined a new company. Tickets created in a trello board suddenly showed up on an old companies repositories. Really really bad. I can(t) believe there is no way to delete an issue. Good news is, we can create an issue in github about this issue and it will NEVER BE DELETED!
        – Volte
        Aug 3 '14 at 6:11




        2




        2




        @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
        – FichteFoll
        Nov 27 '14 at 19:08






        @Volte, actually, this is not entirely true. I've seen numerous notifications from issues that were seemingly spam and would 404 once I clicked them. However, those repos were owned by github staff. So, it is in fact possible to delete issues, but only for github staff.
        – FichteFoll
        Nov 27 '14 at 19:08






        2




        2




        @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
        – Pacerier
        Jun 4 '15 at 6:46




        @AlexandreMartins, Exactly. Archiving is useful when you want to archive and deleting is useful when you actually do want to delete. Serious design flaw with Github.
        – Pacerier
        Jun 4 '15 at 6:46












        up vote
        219
        down vote













        No, the github API only allows you to open/close/reopen issues. Here's the Issues API docs.






        share|improve this answer



















        • 1




          Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
          – jww
          Jun 20 '16 at 4:42






        • 19




          Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
          – Sliq
          Apr 15 '17 at 13:17








        • 4




          Or you can use gitlab.com
          – frmdstryr
          Oct 19 '17 at 14:43










        • Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
          – Mateusz Konieczny
          Jul 28 at 16:11










        • This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
          – StingyJack
          Aug 23 at 12:01















        up vote
        219
        down vote













        No, the github API only allows you to open/close/reopen issues. Here's the Issues API docs.






        share|improve this answer



















        • 1




          Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
          – jww
          Jun 20 '16 at 4:42






        • 19




          Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
          – Sliq
          Apr 15 '17 at 13:17








        • 4




          Or you can use gitlab.com
          – frmdstryr
          Oct 19 '17 at 14:43










        • Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
          – Mateusz Konieczny
          Jul 28 at 16:11










        • This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
          – StingyJack
          Aug 23 at 12:01













        up vote
        219
        down vote










        up vote
        219
        down vote









        No, the github API only allows you to open/close/reopen issues. Here's the Issues API docs.






        share|improve this answer














        No, the github API only allows you to open/close/reopen issues. Here's the Issues API docs.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jul 12 '12 at 17:27

























        answered Jun 21 '10 at 0:59









        Mauricio Scheffer

        86.7k18176263




        86.7k18176263








        • 1




          Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
          – jww
          Jun 20 '16 at 4:42






        • 19




          Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
          – Sliq
          Apr 15 '17 at 13:17








        • 4




          Or you can use gitlab.com
          – frmdstryr
          Oct 19 '17 at 14:43










        • Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
          – Mateusz Konieczny
          Jul 28 at 16:11










        • This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
          – StingyJack
          Aug 23 at 12:01














        • 1




          Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
          – jww
          Jun 20 '16 at 4:42






        • 19




          Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
          – Sliq
          Apr 15 '17 at 13:17








        • 4




          Or you can use gitlab.com
          – frmdstryr
          Oct 19 '17 at 14:43










        • Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
          – Mateusz Konieczny
          Jul 28 at 16:11










        • This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
          – StingyJack
          Aug 23 at 12:01








        1




        1




        Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
        – jww
        Jun 20 '16 at 4:42




        Does this apply to collaborators as well? If so, how do we delete the questions users sometimes ask through the bug tracker instead of out mailing list or Stack Overflow? I find it hard to believe we have to file a Bug Report with GitHub and ask them to delete it.
        – jww
        Jun 20 '16 at 4:42




        19




        19




        Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
        – Sliq
        Apr 15 '17 at 13:17






        Nearly 7 years and thousands of requests later: GitHub still isn't able to delete issues :/ Looks like it will take some time until we have flying cars and skyscrapers on Mars.
        – Sliq
        Apr 15 '17 at 13:17






        4




        4




        Or you can use gitlab.com
        – frmdstryr
        Oct 19 '17 at 14:43




        Or you can use gitlab.com
        – frmdstryr
        Oct 19 '17 at 14:43












        Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
        – Mateusz Konieczny
        Jul 28 at 16:11




        Note that issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.
        – Mateusz Konieczny
        Jul 28 at 16:11












        This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
        – StingyJack
        Aug 23 at 12:01




        This answer is no longer true. I had another user (not GH) alter the title of my issue, change the text of the issue, and then delete the edit history so noone could see the originally reported issue (Which was only critical of some of the content that was both poor quality and unfactual in several ways. It was not obscene, profane, or even really rude)
        – StingyJack
        Aug 23 at 12:01










        up vote
        62
        down vote













        You can edit an existing issue (let's say if it's a duplicate) and you can change the title, description and target milestone to be something completely different. That's as close as you can get to removing the ticket, AFIK.






        share|improve this answer

















        • 4




          Note that it's not possible to edit the title of an issue posted by another user.
          – ocodo
          Dec 1 '12 at 23:41










        • @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
          – Sourabh
          Apr 23 '14 at 13:39








        • 5




          This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
          – Daniel Imms
          Oct 9 '14 at 16:58















        up vote
        62
        down vote













        You can edit an existing issue (let's say if it's a duplicate) and you can change the title, description and target milestone to be something completely different. That's as close as you can get to removing the ticket, AFIK.






        share|improve this answer

















        • 4




          Note that it's not possible to edit the title of an issue posted by another user.
          – ocodo
          Dec 1 '12 at 23:41










        • @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
          – Sourabh
          Apr 23 '14 at 13:39








        • 5




          This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
          – Daniel Imms
          Oct 9 '14 at 16:58













        up vote
        62
        down vote










        up vote
        62
        down vote









        You can edit an existing issue (let's say if it's a duplicate) and you can change the title, description and target milestone to be something completely different. That's as close as you can get to removing the ticket, AFIK.






        share|improve this answer












        You can edit an existing issue (let's say if it's a duplicate) and you can change the title, description and target milestone to be something completely different. That's as close as you can get to removing the ticket, AFIK.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 29 '12 at 18:21









        Kiril

        28.2k22142208




        28.2k22142208








        • 4




          Note that it's not possible to edit the title of an issue posted by another user.
          – ocodo
          Dec 1 '12 at 23:41










        • @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
          – Sourabh
          Apr 23 '14 at 13:39








        • 5




          This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
          – Daniel Imms
          Oct 9 '14 at 16:58














        • 4




          Note that it's not possible to edit the title of an issue posted by another user.
          – ocodo
          Dec 1 '12 at 23:41










        • @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
          – Sourabh
          Apr 23 '14 at 13:39








        • 5




          This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
          – Daniel Imms
          Oct 9 '14 at 16:58








        4




        4




        Note that it's not possible to edit the title of an issue posted by another user.
        – ocodo
        Dec 1 '12 at 23:41




        Note that it's not possible to edit the title of an issue posted by another user.
        – ocodo
        Dec 1 '12 at 23:41












        @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
        – Sourabh
        Apr 23 '14 at 13:39






        @EmacsFodder It is now, title as well as the comment of OP. I am not sure when they added this. Maybe only owner of repo can do this? Probably.
        – Sourabh
        Apr 23 '14 at 13:39






        5




        5




        This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
        – Daniel Imms
        Oct 9 '14 at 16:58




        This doesn't really work anymore due to the audit log GitHub recently introduced github.com/blog/1866-the-new-github-issues
        – Daniel Imms
        Oct 9 '14 at 16:58










        up vote
        31
        down vote













        For posterity: Deleting issues would be a bad thing, since in general they can be targets of associations on github.



        But if you are willing to sacrifice the collaboration info, here is a "whack it with a sledgehammer" approach:




        1. Clone your original repo.

        2. Copy your issues via the Issues API.

        3. Delete the original repo; alternatively, chose a new name for your new repo.

        4. Re-create a new repo based on your clone.

        5. Re-create the issues you want to keep via the Issues API.


        I imagine this could potentially lose a lot of other linking information as well such as forks, pull requests, etc.






        share|improve this answer

















        • 6




          Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
          – Joseph Wright
          May 16 '13 at 5:58






        • 37




          LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
          – Sandeep Raju Prabhakar
          Jul 1 '13 at 21:20






        • 12




          This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
          – Volte
          Aug 3 '14 at 6:14






        • 3




          I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
          – jerseyboy
          Aug 4 '14 at 12:23






        • 1




          What is a "target of association" (in your first paragraph)? (English is not my native language)
          – KajMagnus
          Aug 15 '15 at 7:34

















        up vote
        31
        down vote













        For posterity: Deleting issues would be a bad thing, since in general they can be targets of associations on github.



        But if you are willing to sacrifice the collaboration info, here is a "whack it with a sledgehammer" approach:




        1. Clone your original repo.

        2. Copy your issues via the Issues API.

        3. Delete the original repo; alternatively, chose a new name for your new repo.

        4. Re-create a new repo based on your clone.

        5. Re-create the issues you want to keep via the Issues API.


        I imagine this could potentially lose a lot of other linking information as well such as forks, pull requests, etc.






        share|improve this answer

















        • 6




          Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
          – Joseph Wright
          May 16 '13 at 5:58






        • 37




          LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
          – Sandeep Raju Prabhakar
          Jul 1 '13 at 21:20






        • 12




          This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
          – Volte
          Aug 3 '14 at 6:14






        • 3




          I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
          – jerseyboy
          Aug 4 '14 at 12:23






        • 1




          What is a "target of association" (in your first paragraph)? (English is not my native language)
          – KajMagnus
          Aug 15 '15 at 7:34















        up vote
        31
        down vote










        up vote
        31
        down vote









        For posterity: Deleting issues would be a bad thing, since in general they can be targets of associations on github.



        But if you are willing to sacrifice the collaboration info, here is a "whack it with a sledgehammer" approach:




        1. Clone your original repo.

        2. Copy your issues via the Issues API.

        3. Delete the original repo; alternatively, chose a new name for your new repo.

        4. Re-create a new repo based on your clone.

        5. Re-create the issues you want to keep via the Issues API.


        I imagine this could potentially lose a lot of other linking information as well such as forks, pull requests, etc.






        share|improve this answer












        For posterity: Deleting issues would be a bad thing, since in general they can be targets of associations on github.



        But if you are willing to sacrifice the collaboration info, here is a "whack it with a sledgehammer" approach:




        1. Clone your original repo.

        2. Copy your issues via the Issues API.

        3. Delete the original repo; alternatively, chose a new name for your new repo.

        4. Re-create a new repo based on your clone.

        5. Re-create the issues you want to keep via the Issues API.


        I imagine this could potentially lose a lot of other linking information as well such as forks, pull requests, etc.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 18 '13 at 12:15









        jerseyboy

        1,1121012




        1,1121012








        • 6




          Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
          – Joseph Wright
          May 16 '13 at 5:58






        • 37




          LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
          – Sandeep Raju Prabhakar
          Jul 1 '13 at 21:20






        • 12




          This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
          – Volte
          Aug 3 '14 at 6:14






        • 3




          I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
          – jerseyboy
          Aug 4 '14 at 12:23






        • 1




          What is a "target of association" (in your first paragraph)? (English is not my native language)
          – KajMagnus
          Aug 15 '15 at 7:34
















        • 6




          Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
          – Joseph Wright
          May 16 '13 at 5:58






        • 37




          LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
          – Sandeep Raju Prabhakar
          Jul 1 '13 at 21:20






        • 12




          This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
          – Volte
          Aug 3 '14 at 6:14






        • 3




          I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
          – jerseyboy
          Aug 4 '14 at 12:23






        • 1




          What is a "target of association" (in your first paragraph)? (English is not my native language)
          – KajMagnus
          Aug 15 '15 at 7:34










        6




        6




        Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
        – Joseph Wright
        May 16 '13 at 5:58




        Deleting issues makes sense if there is something unusual happening. For example, I'm moving my code and issues to GitHub and someone has reported a 'new' issue on GitHub before I've finished the move. I need to keep the issue numbers unchanged, so I'll now have to completely hijack this 'wrong' issue.
        – Joseph Wright
        May 16 '13 at 5:58




        37




        37




        LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
        – Sandeep Raju Prabhakar
        Jul 1 '13 at 21:20




        LOL! Even thought your answer is technically right, its a PITA to do this and insane totally!
        – Sandeep Raju Prabhakar
        Jul 1 '13 at 21:20




        12




        12




        This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
        – Volte
        Aug 3 '14 at 6:14




        This answer is not technically correct. It's opinionated. We're not discussing the opinions of deleting an issue. We're discussing a lack of a basic CRUD (D) operation that should be present in most things. It's demeaning and disrespectful for software solutions to restrict basic features in an attempt to "Protect us from ourselves". This is not the U.S. Federal Government; we don't need to be babysat.
        – Volte
        Aug 3 '14 at 6:14




        3




        3




        I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
        – jerseyboy
        Aug 4 '14 at 12:23




        I agree in theory with inconsistencies in interfaces. Telling the OP not to do it was not my main point. It was merely a cautionary statement before I suggested a potentially destructive brute force path to achieving the OP's goal. Besides, StackOverflow isn't the proper venue for criticisms of Github's API. Those should be addressed to Github.
        – jerseyboy
        Aug 4 '14 at 12:23




        1




        1




        What is a "target of association" (in your first paragraph)? (English is not my native language)
        – KajMagnus
        Aug 15 '15 at 7:34






        What is a "target of association" (in your first paragraph)? (English is not my native language)
        – KajMagnus
        Aug 15 '15 at 7:34












        up vote
        28
        down vote













        Public feature request



        I wrote to GitHub in 2014-08 and https://github.com/jdennes replied by email:




        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.




        confirming it was not possible.



        Best workaround so far





        • set the title to something that will never conflict with any search, e.g. a single dot ..



          This may not hide the history of your blunder entirely because of the automatic undeletable "changed the title to" comments.



        • make the body empty



        GitHub staff has the power



        If something is a security issue, contact GitHub staff, they usually reply quickly, and are able to remove issues for good as can be seen at: http://archive.is/OfjVt which has issue 1 and 3 but no 2.






        share|improve this answer



























          up vote
          28
          down vote













          Public feature request



          I wrote to GitHub in 2014-08 and https://github.com/jdennes replied by email:




          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.




          confirming it was not possible.



          Best workaround so far





          • set the title to something that will never conflict with any search, e.g. a single dot ..



            This may not hide the history of your blunder entirely because of the automatic undeletable "changed the title to" comments.



          • make the body empty



          GitHub staff has the power



          If something is a security issue, contact GitHub staff, they usually reply quickly, and are able to remove issues for good as can be seen at: http://archive.is/OfjVt which has issue 1 and 3 but no 2.






          share|improve this answer

























            up vote
            28
            down vote










            up vote
            28
            down vote









            Public feature request



            I wrote to GitHub in 2014-08 and https://github.com/jdennes replied by email:




            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.




            confirming it was not possible.



            Best workaround so far





            • set the title to something that will never conflict with any search, e.g. a single dot ..



              This may not hide the history of your blunder entirely because of the automatic undeletable "changed the title to" comments.



            • make the body empty



            GitHub staff has the power



            If something is a security issue, contact GitHub staff, they usually reply quickly, and are able to remove issues for good as can be seen at: http://archive.is/OfjVt which has issue 1 and 3 but no 2.






            share|improve this answer














            Public feature request



            I wrote to GitHub in 2014-08 and https://github.com/jdennes replied by email:




            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.




            confirming it was not possible.



            Best workaround so far





            • set the title to something that will never conflict with any search, e.g. a single dot ..



              This may not hide the history of your blunder entirely because of the automatic undeletable "changed the title to" comments.



            • make the body empty



            GitHub staff has the power



            If something is a security issue, contact GitHub staff, they usually reply quickly, and are able to remove issues for good as can be seen at: http://archive.is/OfjVt which has issue 1 and 3 but no 2.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Apr 24 at 2:59

























            answered Aug 15 '14 at 9:47









            Ciro Santilli 新疆改造中心 六四事件 法轮功

            131k29513442




            131k29513442






















                up vote
                9
                down vote













                You can delete the entire repo if it's really important.






                share|improve this answer

















                • 3




                  +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                  – Dan Lugg
                  May 4 '17 at 0:35















                up vote
                9
                down vote













                You can delete the entire repo if it's really important.






                share|improve this answer

















                • 3




                  +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                  – Dan Lugg
                  May 4 '17 at 0:35













                up vote
                9
                down vote










                up vote
                9
                down vote









                You can delete the entire repo if it's really important.






                share|improve this answer












                You can delete the entire repo if it's really important.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 3 '17 at 0:01









                Dorian

                12.5k37383




                12.5k37383








                • 3




                  +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                  – Dan Lugg
                  May 4 '17 at 0:35














                • 3




                  +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                  – Dan Lugg
                  May 4 '17 at 0:35








                3




                3




                +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                – Dan Lugg
                May 4 '17 at 0:35




                +1'd to fix the -1. This might be absurd, but it's the only way to actually remove the content. Baby, bath water, and kitchen sink.
                – Dan Lugg
                May 4 '17 at 0:35










                up vote
                0
                down vote













                You could by just asking to github to ban the user that created the issue 😁



                Source: https://github.com/isaacs/github/issues/253#issuecomment-290944938






                share|improve this answer



























                  up vote
                  0
                  down vote













                  You could by just asking to github to ban the user that created the issue 😁



                  Source: https://github.com/isaacs/github/issues/253#issuecomment-290944938






                  share|improve this answer

























                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    You could by just asking to github to ban the user that created the issue 😁



                    Source: https://github.com/isaacs/github/issues/253#issuecomment-290944938






                    share|improve this answer














                    You could by just asking to github to ban the user that created the issue 😁



                    Source: https://github.com/isaacs/github/issues/253#issuecomment-290944938







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Aug 18 '17 at 5:54

























                    answered Aug 17 '17 at 16:34









                    Philippe

                    11.6k42543




                    11.6k42543






















                        up vote
                        0
                        down vote













                        Users are unable to do this, including repository owner.



                        But issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.






                        share|improve this answer

























                          up vote
                          0
                          down vote













                          Users are unable to do this, including repository owner.



                          But issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.






                          share|improve this answer























                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            Users are unable to do this, including repository owner.



                            But issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.






                            share|improve this answer












                            Users are unable to do this, including repository owner.



                            But issues can be deleted by Github support. One may contact them and request deletion. It may be delayed or refused but it is an available option that can be used.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Jul 28 at 16:12









                            Mateusz Konieczny

                            73211028




                            73211028






















                                up vote
                                0
                                down vote













                                Still impossible. Another workaround to the ones suggested in the other answers is to label the issue as "deleted" (or any other label you might fancy better), to be able to filter them out if you use the github API to retrieve them. Obviously you should use that specific label only for this purpose, setting the label when you close the issue.






                                share|improve this answer





















                                • Now it is possible
                                  – Radium Zheng
                                  Nov 8 at 22:13










                                • yes it is at last
                                  – Mark Kaplun
                                  Nov 9 at 5:41















                                up vote
                                0
                                down vote













                                Still impossible. Another workaround to the ones suggested in the other answers is to label the issue as "deleted" (or any other label you might fancy better), to be able to filter them out if you use the github API to retrieve them. Obviously you should use that specific label only for this purpose, setting the label when you close the issue.






                                share|improve this answer





















                                • Now it is possible
                                  – Radium Zheng
                                  Nov 8 at 22:13










                                • yes it is at last
                                  – Mark Kaplun
                                  Nov 9 at 5:41













                                up vote
                                0
                                down vote










                                up vote
                                0
                                down vote









                                Still impossible. Another workaround to the ones suggested in the other answers is to label the issue as "deleted" (or any other label you might fancy better), to be able to filter them out if you use the github API to retrieve them. Obviously you should use that specific label only for this purpose, setting the label when you close the issue.






                                share|improve this answer












                                Still impossible. Another workaround to the ones suggested in the other answers is to label the issue as "deleted" (or any other label you might fancy better), to be able to filter them out if you use the github API to retrieve them. Obviously you should use that specific label only for this purpose, setting the label when you close the issue.







                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Sep 20 at 5:12









                                Mark Kaplun

                                192111




                                192111












                                • Now it is possible
                                  – Radium Zheng
                                  Nov 8 at 22:13










                                • yes it is at last
                                  – Mark Kaplun
                                  Nov 9 at 5:41


















                                • Now it is possible
                                  – Radium Zheng
                                  Nov 8 at 22:13










                                • yes it is at last
                                  – Mark Kaplun
                                  Nov 9 at 5:41
















                                Now it is possible
                                – Radium Zheng
                                Nov 8 at 22:13




                                Now it is possible
                                – Radium Zheng
                                Nov 8 at 22:13












                                yes it is at last
                                – Mark Kaplun
                                Nov 9 at 5:41




                                yes it is at last
                                – Mark Kaplun
                                Nov 9 at 5:41





                                protected by Josh Crozier Nov 27 '17 at 0:53



                                Thank you for your interest in this question.
                                Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                Would you like to answer one of these unanswered questions instead?



                                -

                                這個網誌中的熱門文章

                                Xamarin.form Move up view when keyboard appear

                                圖片
                                .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I'm trying to build a Chat app UI, the idea of the Layout was pretty simple: When the input bar is focused, keyboard show up and "push" up the chat bar, as it's a grid, the ListView will resize to fit the screen: I update the input bar's margin to "push" it up: NSValue result = (NSValue)args.Notification.UserInfo.ObjectForKey(new NSString(UIKeyboard.FrameEndUserInfoKey)); CGSize keyboardSize = result.RectangleFValue.Size; if (Element != null){ Element.Margin = new Thickness(0, 0, 0,keyboardSize.Height); //push the entry up to keyboard height when keyboard is activated } And this is ...
                                閱讀完整內容

                                Post-Redirect-Get with Spring WebFlux and Thymeleaf

                                圖片
                                .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 2 Can someone explain to me how to implement the post-redirect-get pattern in Spring WebFlux and Thymeleaf? What subscribes on the database save method? @GetMapping("/register") public String showRegisterForm(Model model) { model.addAttribute("user", new User()); return "register"; } @PostMapping public String processRegisterForm(@Valid User user, BindingResult bindingResult) { if (bindingResult.hasErrors()) { return "register"; } else { userRepository.save(user); //what subscribes on this? //how to redirect on e.g. "/login"? ...
                                閱讀完整內容

                                Anylogic : not able to use stopDelay()

                                圖片
                                -2 I am building a railway station model. I want a train to depart when I click a button. I want to call stopDelay() for that but I am not sure how to do that and from which place. anylogic share | improve this question asked Nov 23 '18 at 10:12 Anupam Singh Anupam Singh 1 Hi Anupam, welcome to SOF. Please check how to ask good questions, see link below. Your question is...
                                閱讀完整內容