This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-10-06
Channels
- # aleph (15)
- # announcements (2)
- # babashka (121)
- # beginners (62)
- # biff (6)
- # cherry (2)
- # cider (51)
- # clerk (30)
- # cljs-dev (5)
- # clojure (77)
- # clojure-austin (2)
- # clojure-europe (10)
- # clojure-germany (6)
- # clojure-nl (1)
- # clojure-norway (19)
- # clojure-romania (1)
- # clojure-uk (3)
- # clojurescript (16)
- # core-typed (7)
- # cursive (17)
- # datomic (12)
- # deps-new (11)
- # emacs (7)
- # events (2)
- # fulcro (5)
- # honeysql (2)
- # hyperfiddle (32)
- # introduce-yourself (1)
- # jobs-discuss (2)
- # membrane (18)
- # missionary (2)
- # music (5)
- # polylith (7)
- # reagent (26)
- # releases (5)
- # testing (32)
- # tools-build (14)
- # tools-deps (7)
- # xtdb (8)
Would notification for only the commits to the main branch be more appropriate or are you seeking feedback on each push to the develop branch?
The develop branch is the only branch I work on (I prefer that name to main).
Since deps-new
is git-only and also references itself, the release process is prep for interim release, make that release, prep for the full release, make that release (and delete the interim release), add the full release sha back into the readme etc.
I'll see if I can configure it to not report commits (yup, done!), and maybe I'll switch to doing the interim releases as tags instead...
It's always interesting to figure out what is the right level to communicate : 😁