How to reduce the actual size of my github review? (not just my local check)

I deleted some large files from my repo after the following instructions:

http://help.github.com/remove-sensitive-data

However, if I make a new clone from my main repo, I will still pull the deleted data. I suspect this because of this:

โ€œBe warned that forcing does not erase the commit on the remote repo, it just introduces new ones and moves the pointer to the pointer to point to them. If you are concerned that users accessing the bad commit directly through SHA1, you will must remove the repo and recreate it. "

I tried dragging and dropping commits to a new repo, and although it has no extra data, it also skips all my github issues.

Two (related) questions: - is there a way to push a peeled repo to the main repo? - if not, is there a way to transfer problems from the main repo to a new repo?

+4
source share
2 answers

Well, after back and forth with GitHub to support the team very well (thanks to Tekkub!), We figured out what was going on.

The answer was that repo had tags that contained pointers to old data. The solution was to force click tags, ensuring that the old tags are deleted (and therefore the old data received garbage collection).

+2
source

If you are still receiving material that you deleted during cloning, then it is still mentioned somewhere. Check out git branch -va on the new clone, you probably have a branch pointing to the commits you want to delete.

0
source

All Articles