Not logged in. or Create a profile

Home → Repo issues →

Subject: Deleted repo doesn't disappear

Original Post 's Avatar

kaafarani.ali

06 Nov, 2009 05:18 PM

Hi and thanks for reading!

I (murr4y) recently deleted a repository ("backer"), but it seems to still be there.
It doesn't go away from my profile, however the github web page gives a 404. But not right now:

The reason for that is I want to show the differences, so I created two new repos on github: "backer" and "backer-proper". Then I pushed from the same local repo to BOTH of them. So they should be equal, right? No, compare the commit SHA's. Most of them are different.

What's even weirder is that if I rename the backer repo to something else, suddenly that repo is equal to the other one (backer-proper)! With that I mean the SHA's. So something is obviously "sticky" about the old backer repo. Hopefully this makes more sense to you guys than to me.

What happend was that i rebased the entire repo locally so I wanted to repush it to github. Instead of actually deleting it I tried deleting the master branch on github and then push that branch back, but I guess maybe that might have screwed things up. So I tried deleting the entire repo from github, but as described above, that doesn't work properly.

Are you guys able to fix this or tell me what I've done wrong and need to do? :)

Thanks,
murr4y

  1. Support Staff 2 Posted by Tekkub on 06 Nov, 2009 11:43 PM

    Tekkub's Avatar

    Are you comparing things on the site, or in your local clones? Pages on the site are cached, and things like renaming or using a repo name that previously existed can dig up those old caches. Let me know exactly what URLs you're looking at and I can clear caches on them.

  2. 3 Posted by Ali Kaafarani on 07 Nov, 2009 12:01 AM

    Ali Kaafarani's Avatar

    I am comparing on the site. From what I can tell, you're right and caching does indeed seem to be the issue.

    The URL to the repo with the problems is:
    http://github.com/murr4y/backer/

    When I clone it, the local (cloned) repository is fine. It's just the web site that shows some old, probably cached, stuff.

    Just for the record, is this something that would clear out automatically if I hadn't bothered you guys with it? :)

    Thanks!

  3. Support Staff 4 Posted by Tekkub on 07 Nov, 2009 12:23 AM

    Tekkub's Avatar

    I've cleared the cache for you. Usually pushing new commits is the best way to clear it. Force-pushes and repo admin actions don't always do it.

Comments are currently closed for this discussion. You can start a new one.

2 people watching.

  • New Issue

  • Conversation Started

  • The issue is resolved

    No more actions from GitHub or the discussion starter are required.

  • Unresolve the issue

Recent Discussions

23 Nov, 2009 07:57 AM GitHub pages are not working
23 Nov, 2009 06:39 AM The private gist popup notice appears at the bottom of the page.
23 Nov, 2009 05:11 AM Spam repos
22 Nov, 2009 05:29 PM manual Fork Queue instructions
22 Nov, 2009 04:04 PM Yearly Subscriptions

 

22 Nov, 2009 01:58 PM repo exists but web portion "doesn't exist"
22 Nov, 2009 06:55 AM How to link to in-page anchors in the wiki
22 Nov, 2009 05:01 AM Source View Breaking
22 Nov, 2009 03:33 AM Merging committers in history
22 Nov, 2009 03:24 AM Broken repo?