This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-09
Channels
- # announcements (4)
- # aws (3)
- # babashka (86)
- # babashka-sci-dev (31)
- # beginners (171)
- # biff (15)
- # calva (3)
- # clerk (47)
- # cljdoc (11)
- # clojure (59)
- # clojure-dev (11)
- # clojure-europe (122)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-norway (4)
- # clojure-uk (2)
- # clojurescript (40)
- # cursive (5)
- # data-science (3)
- # datahike (1)
- # datomic (5)
- # fulcro (9)
- # graalvm (8)
- # hyperfiddle (17)
- # introduce-yourself (1)
- # java (28)
- # jobs (1)
- # malli (11)
- # membrane (9)
- # missionary (1)
- # nbb (1)
- # off-topic (5)
- # other-languages (1)
- # pedestal (1)
- # re-frame (4)
- # reagent (16)
- # releases (3)
- # remote-jobs (3)
- # shadow-cljs (83)
- # spacemacs (1)
- # sql (5)
- # tools-deps (28)
- # xtdb (15)
if I forgot to push the tag and deployed to clojars, and now the build failed because cljdoc can't find the right tag, can i trigger a new build or does that hvae to be one of you?
it should work now, i've pushed the tag
There's a near-invisible button that say "rebuild" just to the left of the GitHub link, top-right, where you can ask cljdoc to have another go at the import & analysis...
It's really hard to see but it's there...
Omg haha thanks
deliberately hard to see, I was told, iirc
yeah, that's my understanding too @U02N27RK69K, a little ui hack to avoid having to come up with accounts/permissions, and it seems to be working ok these past years.
it's a trade-off, I think. only people who ask will learn about it so some people out there just don't know and are unhappy with a broken build, but we also have much less to maintain to support it
yep. I think we were toying with the idea of making the rebuild more visible but implementing some rate limiting.... ya https://github.com/cljdoc/cljdoc/issues/672.