xjava has not that many contributors and it would be fine with me to make this change and re-clone.

We could also give the rewritten repo a new name and declare the old one dead while leaving it in place.

Are there other references to commit hashes in this repo (and related) that would be broken by rewriting history in this way? (Eg used for production deploys or in logs etc)

On Aug 31, 2014, at 15:18, Katrina Owen [email protected] wrote:

I made a really stupid choice a while back to commit the cross-compiled
binaries for configlet (the tool that sanity-checks the config.json
against the implemented problems) into the repository itself.

Those binaries are HUGE, and every time they change the entire 4 or 5 megs get
recommitted. This means that cloning the repository takes a ridiculously long
time.

I've added a script that can be run on travis to grab the latest release from
the configlet repository (bin/fetch-configlet), and travis is set up to run
this now instead of using the committed binary.

I would really like to thoroughly delete the binaries from the entire git
history, but this will break all the existing clones and forks.

The commands I would run are:

ensure this happens on an up-to-date master

git checkout master && git fetch origin && git reset --hard origin/master

delete from history

git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch bin/configlet-*' --prune-empty

clean up

rm -rf .git/refs/original/
git reflog expire --all
git gc --aggressive --prune

push up the new master, force override existing master branch

git push -fu origin master
If we do this everyone who has a fork will need to make sure that their master
is reset to the new upstream master:

git checkout master
git fetch upstream master
git reset --hard upstream/master
git push -fu origin master
We can at-mention (@) all the contributors and everyone who has a fork here in this
issue if we decide to do it.

The important question though, is: Is it worth doing?

Do you have any other suggestions of how to make sure this doesn't confuse people and break their
repository if we do proceed with this change?

—
Reply to this email directly or view it on GitHub.

from java.

I'm going to have to redo the submodules in the x-api repository (problems API), but that's fine.

I'll go ahead and kick this off.

from java.

Heads up - if you want to contribute to this repository in the future you're going to need to reset or reclone.

/ cc
@wdjunaidi
@sagarsane
@sjakobi
@codingricky
@michaelavila

from java.

Thanks for the heads up!
On Aug 31, 2014 7:42 PM, "Katrina Owen" [email protected] wrote:

Closed #8 #8.

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

from java.