This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-06
Channels
- # adventofcode (10)
- # ai (2)
- # aleph (2)
- # announcements (21)
- # beginners (25)
- # calva (7)
- # cider (19)
- # clj-kondo (28)
- # clj-on-windows (3)
- # cljdoc (6)
- # clojure (80)
- # clojure-dev (15)
- # clojure-europe (29)
- # clojure-italy (3)
- # clojure-nl (37)
- # clojure-uk (4)
- # clojurescript (3)
- # cloverage (1)
- # conjure (6)
- # core-async (2)
- # cursive (17)
- # datalevin (9)
- # datomic (7)
- # deps-new (23)
- # emacs (4)
- # figwheel-main (6)
- # fulcro (6)
- # honeysql (19)
- # improve-getting-started (4)
- # inf-clojure (2)
- # introduce-yourself (5)
- # jobs (1)
- # leiningen (6)
- # lsp (73)
- # malli (1)
- # nrepl (2)
- # off-topic (37)
- # polylith (9)
- # quil (2)
- # reitit (16)
- # releases (2)
- # remote-jobs (6)
- # rewrite-clj (38)
- # shadow-cljs (1)
- # tools-build (1)
@lee: I was going to say no, but it appears you might be right and there was briefly a 75mb committed at one point in the history
I think it may even have been on a branch that never got merged
Yeah looks like a 75mb data file for performance testing on a perf test branch that I never merged… I should be able to rewrite/purge that branch and gc the repo; and see if that fixes it. Thanks for the pointer 🙇
I’ll let you know if after I do that if it fixes it
Ok I migrated those branches to git-lfs and force pushed them which means a newly cloned repo is now just 300kb. Importantly it means the docs now build: https://cljdoc.org/d/grafter/matcha.alpha/0.3.2/doc/readme Many thanks for your help @lee 🙇
@rickmoynihan glad my guess worked for you. And thanks for adding to the existing issue.