1

I closed an issue via commit message of a commit. But then I decided to revert the pushed commit with the git rebase command. Deleting worked fine; gitk shows the cleaned history as intented.

However, in our githup repository, the issue is still closed and the referencing commit is clickable. That is, I can see what I did (and reverted).

Is this behaviour intended? How can I also clean the issue log after I have deleted a commit?

Improve this question
8
  • git revert is fine, but rewriting history that's already pushed is something you should never do. But either way, you have to reopen the issue manually, since it's not always desirable to reopen an issue after a revert.
    – Alexia Luna
    Dec 21, 2014 at 18:42
  • Well, the only problem you face is that others maybe already pulled the changes and worked with it. In this case, however, I am the only contributor.
    – MERose
    Dec 21, 2014 at 19:08
  • Just because you're the only contributor doesn't mean nobody clones your repo. A force push will cause trouble (although easy to fix if you know how to) even with an unchanged local tree.
    – Alexia Luna
    Dec 21, 2014 at 19:09
  • My repo is private, too.
    – MERose
    Dec 21, 2014 at 19:10
  • You should have started with that.
    – Alexia Luna
    Dec 21, 2014 at 19:11

1 Answer 1

Reset to default
0

Here is the answer I received from github's support:

  • Issues can't be reopened if the commit is removed from history but they will consider it as an improvement.
  • Therefore issues have to be reopened manually.
  • The commit will be visible (after clicking on the link in the issue's log) unless a garbage collection cycle removes it. The log will then say "Commit has since been removed from the repository and is no longer available."
  • They can run a garbage collection cycle on a commit on request because the normal user cannot.
Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .