Repository is ~150 MB

[ElDeveloper]

When #52 was merged, the commit history seems to have been duplicated, when I pulled from upstream/master to my clone, the size of the repo went from 60 MB to 147 MB.

When I clone from upstream/master the repo's size is 146 MB.

[squirrelo]

Welp. Apparently by trying to remove giant files it created....giant files. Not sure how to fix that.

This may also be a good time to talk about removing the prototypes folder though. I don't see why it needs to live in the repo itself.

[ElDeveloper]

Would anyone mind if I do this today?

[ElDeveloper]

Please reply if so by 8pm MST.

[antgonza]

Do it!
On Jun 23, 2014 6:12 PM, "Yoshiki Vázquez Baeza" notifications@github.com
wrote:

Please reply if so by 8pm MST.

—
Reply to this email directly or view it on GitHub
#59 (comment).

[wasade]

+1
On Jun 23, 2014 6:22 PM, "Antonio Gonzalez" notifications@github.com
wrote:

Do it!
On Jun 23, 2014 6:12 PM, "Yoshiki Vázquez Baeza" notifications@github.com

wrote:

Please reply if so by 8pm MST.

—
Reply to this email directly or view it on GitHub
#59 (comment).

—
Reply to this email directly or view it on GitHub
#59 (comment).

[josenavas]

Kill it! I don't think there is anybody working on a branch right now!

[josenavas]

Also, can you remove the prototypes?

[squirrelo]

Why did this re-open?

[ElDeveloper]

Ah 'cause I haven't fixed the problem, working on it. Stay tuned.

On (Jun-23-14|22:52), Joshua Shorenstein wrote:

Why did this re-open?

---

Reply to this email directly or view it on GitHub:
#59 (comment)

[squirrelo]

It's tiny for me. Did you re-fork it? I had to do that to wipe out all the built up branches.

[ElDeveloper]

It took me a while to figure it out, the history is gone.

To set your clones to the same state as the upstream/master ref, all you have to do now is run the following commands (make sure there are no commits that you would be losing by overwriting the commit history):

git pull -f upstream master
git push -f origin master

I recommend this instead of other alternatives as this way you will conserve some repo-specific settings, like your remotes, other branches etc. Note that if you had branches that bifurcated off of the previous master and you submit a PR, it is going to drag the full history, so please avoid this situation.

[antgonza]

Repo/history is smaller but prototypes are still there, can you remove
them?

[ElDeveloper]

Hmmm, I'm pretty sure I removed it, are you sure that's not an empty folder?

Yoshiki Vázquez-Baeza

On Jun 24, 2014, at 6:06 AM, Antonio Gonzalez notifications@github.com wrote:

Repo/history is smaller but prototypes are still there, can you remove
them?
—
Reply to this email directly or view it on GitHub.

[teravest]

This is putting me in merge conflict hell... I think 35 files have
conflicts when I try and do this... anyone have any idea how to avoid this?

On Tue, Jun 24, 2014 at 8:00 AM, Yoshiki Vázquez Baeza <
notifications@github.com> wrote:

Hmmm, I'm pretty sure I removed it, are you sure that's not an empty
folder?

Yoshiki Vázquez-Baeza

On Jun 24, 2014, at 6:06 AM, Antonio Gonzalez notifications@github.com
wrote:

Repo/history is smaller but prototypes are still there, can you remove
them?
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub
#59 (comment).

[josenavas]

Thanks Yoshiki, that seems to work for me.
I still can see the prototypes on my end (and they are not empty folders) but they do not appear on the github repo, so I'll assume is some kind of gitignore or something like that?

[antgonza]

My guess is that you needed to first update to the latest version on the
repo before @ElDeveloper's changes. One option is to erase everything and
start from scratch ...

[josenavas]

I'll porbably re-fork the repo....

[teravest]

I think i got

I did
git fetch --all
git reset --hard upstream/master
git pull -f upstream master
git push -f origin master

I do not appear to have the prototypes

On Tue, Jun 24, 2014 at 8:47 AM, josenavas notifications@github.com wrote:

I'll porbably re-fork the repo....

—
Reply to this email directly or view it on GitHub
#59 (comment).

[josenavas]

Thanks @teravest that worked for me!

[antgonza]

My repo was messed up but now is fine. Thanks for the clean up.