Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup git repository #112

Closed
mitar opened this issue Sep 24, 2016 · 2 comments
Closed

Cleanup git repository #112

mitar opened this issue Sep 24, 2016 · 2 comments

Comments

@mitar
Copy link
Contributor

mitar commented Sep 24, 2016

This git repository is pretty strange and contains a lot of commits which are not really part of Blaze at all. For example if you look into contributors, you can see many contributors for many changes which are not related to any of Blaze directories, like:

(Those are just examples, picked randomly.)

Currently repository is then pretty huge. And I have no idea how to clean those up. Can somebody try removing them and report here instructions how to do it?

@mitar
Copy link
Contributor Author

mitar commented Dec 5, 2016

I pruned the repository: https://github.com/mitar/blaze-pruned

Now history is only Blaze related. I used this tool: https://github.com/ajdruff/git-splits

And run it with:

git splits -b new packages/blaze packages/blaze-html-templates packages/blaze-tools packages/caching-html-compiler packages/html-tools packages/htmljs packages/spacebars packages/spacebars-compiler packages/spacebars-tests packages/static-html packages/templating packages/templating-tools packages/ui attrs.js backcompat.js builtins.js dombackend.js domrange.js events.js exceptions.js lookup.js materializer.js microscore.js package.js preamble.js render_tests.js template.js view.js view_tests.js tojs.js tokens.js token_tests.js component.js html.js materialize.js render.js sequence.js var.js var.md renderpoint.js reactivevar.js caching-html-compiler.js stringifiers.js blaze.js compile_tests.js spacebars.js spacebars_tests.js syntax.md templatetag.js codegen.js templatetag.js optimizer.js compiler.js compiler_output_tests.coffee template_tests.html template_tests.js global_template_object.js plugin/compile-templates.js plugin/html_scanner.js scanner_tests.js dynamic.html dynamic.js dynamic_tests.html dynamic_tests.js plugin/compile-templates.js templating.js deftemplate.js versions.json throw-compile-error.js templating-tools.js code-generation.js compile-tags-with-spacebars.js html-scanner-tests.js html-scanner.js templating-tools.js static-html.js charref.js charref_tests.js exports.js parse.js parse_tests.js scanner.js tokenize.js tokenize_tests.js spacebars-compiler.js spacebars-compiler-test-versions.json spacebars-compiler-versions.json react.js utils.js tohtml.js htmljs_test.js htmljs_test.js visitors.js assets/markdown_basic.html assets/markdown_each1.html assets/markdown_each2.html assets/markdown_if1.html assets/markdown_if2.html template_tests_server.js templating_tests.html templating_tests.js spacebars-runtime.js html_scanner.js compileTemplates-versions.json templating-test-versions.json templating-versions.json plugin/html2_scanner.js .npm/plugin/compileTemplatesBatch/.gitignore .npm/plugin/compileTemplatesBatch/README .npm/plugin/compileTemplatesBatch/npm-shrinkwrap.json evaluate-handlebars.js parse-handlebars.js spacebars-test-versions.json spacebars-versions.json old_templates.js old_templates_tests.js template_tests_collections.js spacebars-tests-test-versions.json spacebars-tests-versions.json codegen2.js htmljs-test-versions.json htmljs-versions.json html-tools-test-versions.json html-tools-versions.json packages/liveui packages/liverange packages/domutils packages/universal-events packages/spark packages/html packages/handlebars packages/html5-tokenizer tests/liverange

So this removes all Meteor history which is currently in this repository and it is making it huge (and also makes all states strange). I will force push to this repository soon the cleaned version. This will destroy pull request references in this repository, but it will make it cleaner in the future.

@mitar
Copy link
Contributor Author

mitar commented Dec 30, 2016

Force pushed a cleaned repository to this repository. Sadly this means everyone has to re-clone this repository if they want to work on it. And pull requests has to be remade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant