How to completely remove an issue from GitHub?

up vote
376
down vote

favorite

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

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

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

|
show 4 more comments

up vote
376
down vote

favorite

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

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

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

|
show 4 more comments

up vote
376
down vote

favorite

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

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

2,99021619

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

github privacy issue-tracking

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

2,99021619

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

2,99021619

edited Aug 17 '15 at 22:52

kenorb

63k27377386

edited Aug 17 '15 at 22:52

kenorb

63k27377386

edited Aug 17 '15 at 22:52

kenorb

63k27377386

asked Jun 21 '10 at 0:32

YGL

2,99021619

asked Jun 21 '10 at 0:32

YGL

2,99021619

asked Jun 21 '10 at 0:32

YGL

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

|
show 4 more comments

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

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

@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 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

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

|
show 4 more comments

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

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

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

add a comment |

up vote
219
down vote

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

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

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

|
show 2 more comments

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.

answered Jun 29 '12 at 18:21

Kiril

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

add a comment |

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:

Clone your original repo.

Copy your issues via the Issues API.

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

Re-create a new repo based on your clone.

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.

answered Mar 18 '13 at 12:15

jerseyboy

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

|
show 2 more comments

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.

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

add a comment |

up vote
9
down vote

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

answered Feb 3 '17 at 0:01

Dorian

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

add a comment |

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

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

add a comment |

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.

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

add a comment |

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.

answered Sep 20 at 5:12

Mark Kaplun

192111

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

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

add a comment |

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

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

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

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

add a comment |

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

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

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

add a comment |

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

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

822k28425833101

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

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

822k28425833101

edited Nov 7 at 18:24

answered Dec 18 '13 at 8:17

VonC

822k28425833101

answered Dec 18 '13 at 8:17

VonC

822k28425833101

answered Dec 18 '13 at 8:17

VonC

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

add a comment |

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

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

@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

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

@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

@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

add a comment |

up vote
219
down vote

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

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

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

|
show 2 more comments

up vote
219
down vote

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

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

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

|
show 2 more comments

up vote
219
down vote

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

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

86.7k18176263

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

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

86.7k18176263

edited Jul 12 '12 at 17:27

answered Jun 21 '10 at 0:59

Mauricio Scheffer

86.7k18176263

answered Jun 21 '10 at 0:59

Mauricio Scheffer

86.7k18176263

answered Jun 21 '10 at 0:59

Mauricio Scheffer

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

|
show 2 more comments

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

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

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

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

|
show 2 more comments

up vote
62
down vote

answered Jun 29 '12 at 18:21

Kiril

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

add a comment |

up vote
62
down vote

answered Jun 29 '12 at 18:21

Kiril

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

add a comment |

up vote
62
down vote

answered Jun 29 '12 at 18:21

Kiril

28.2k22142208

answered Jun 29 '12 at 18:21

Kiril

28.2k22142208

answered Jun 29 '12 at 18:21

Kiril

28.2k22142208

answered Jun 29 '12 at 18:21

Kiril

28.2k22142208

answered Jun 29 '12 at 18:21

Kiril

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

add a comment |

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

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

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

add a comment |

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:

Clone your original repo.

Copy your issues via the Issues API.

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

Re-create a new repo based on your clone.

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.

answered Mar 18 '13 at 12:15

jerseyboy

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

|
show 2 more comments

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:

Clone your original repo.

Copy your issues via the Issues API.

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

Re-create a new repo based on your clone.

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.

answered Mar 18 '13 at 12:15

jerseyboy

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

|
show 2 more comments

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:

Clone your original repo.

Copy your issues via the Issues API.

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

Re-create a new repo based on your clone.

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.

answered Mar 18 '13 at 12:15

jerseyboy

1,1121012

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:

Clone your original repo.

Copy your issues via the Issues API.

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

Re-create a new repo based on your clone.

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.

answered Mar 18 '13 at 12:15

jerseyboy

1,1121012

answered Mar 18 '13 at 12:15

jerseyboy

1,1121012

answered Mar 18 '13 at 12:15

jerseyboy

1,1121012

answered Mar 18 '13 at 12:15

jerseyboy

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

|
show 2 more comments

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

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

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

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

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

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

|
show 2 more comments

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.

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

add a comment |

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.

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

add a comment |

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.

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

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.

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

edited Apr 24 at 2:59

answered Aug 15 '14 at 9:47

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

131k29513442

answered Aug 15 '14 at 9:47

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

131k29513442

answered Aug 15 '14 at 9:47

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

131k29513442

add a comment |

up vote
9
down vote

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

answered Feb 3 '17 at 0:01

Dorian

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

add a comment |

up vote
9
down vote

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

answered Feb 3 '17 at 0:01

Dorian

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

add a comment |

up vote
9
down vote

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

answered Feb 3 '17 at 0:01

Dorian

12.5k37383

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

answered Feb 3 '17 at 0:01

Dorian

12.5k37383

answered Feb 3 '17 at 0:01

Dorian

12.5k37383

answered Feb 3 '17 at 0:01

Dorian

12.5k37383

answered Feb 3 '17 at 0:01

Dorian

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

add a comment |

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

add a comment |

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

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

add a comment |

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

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

add a comment |

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

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

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

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

edited Aug 18 '17 at 5:54

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

answered Aug 17 '17 at 16:34

Philippe

11.6k42543

add a comment |

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.

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

add a comment |

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.

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

add a comment |

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.

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

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.

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

answered Jul 28 at 16:12

Mateusz Konieczny

73211028

add a comment |

up vote
0
down vote

answered Sep 20 at 5:12

Mark Kaplun

192111

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

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

add a comment |

up vote
0
down vote

answered Sep 20 at 5:12

Mark Kaplun

192111

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

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

add a comment |

up vote
0
down vote

answered Sep 20 at 5:12

Mark Kaplun

192111

answered Sep 20 at 5:12

Mark Kaplun

192111

answered Sep 20 at 5:12

Mark Kaplun

192111

answered Sep 20 at 5:12

Mark Kaplun

192111

answered Sep 20 at 5:12

Mark Kaplun

192111

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

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

add a comment |

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

add a comment |

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

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Wsrtjtyk