This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-07
Channels
- # announcements (27)
- # babashka (29)
- # beginners (280)
- # calva (34)
- # cider (4)
- # circleci (11)
- # cljfx (10)
- # cljsrn (1)
- # clojure (526)
- # clojure-dev (9)
- # clojure-europe (42)
- # clojure-finland (5)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-taiwan (2)
- # clojure-uk (14)
- # clojurescript (40)
- # clr (43)
- # community-development (5)
- # css (4)
- # cursive (7)
- # duct (82)
- # events (1)
- # fulcro (72)
- # garden (44)
- # hoplon (3)
- # java (40)
- # jobs (4)
- # juxt (1)
- # luminus (53)
- # meander (13)
- # off-topic (26)
- # pathom (14)
- # pedestal (3)
- # portal (2)
- # rdf (3)
- # re-frame (54)
- # releases (10)
- # remote-jobs (3)
- # sci (74)
- # shadow-cljs (47)
- # startup-in-a-month (5)
- # testing (9)
- # tools-deps (73)
- # vim (12)
Howdy! I’ve built a GitHub Action to check your deps.edn files for outdated dependencies, and to automatically create PRs for each upgrade. Give it a try: https://github.com/nnichols/clojure-dependency-update-action • Thanks to @tessellator for the original shell script this was based off of!
Really cool! Does it checks for already open PRs by the GH action itself? Otherwise, each push it'll open a PR? 😅
The branch names for each old-version:new-version pair would be identical, and the github cli accurately prevents you from opening more than one PR against a single branch.
It ought to log a message that the PR exists and move on to the next stale dependency iirc
Cool! I'll add a refence to antq's README (PR is also welcomed!) https://github.com/liquidz/antq#github-actions
Amazing @UCZ5ZDJKF!
Release version 2021.01.07-12.28.44 which adds a new "add-import-to-namespace" refactoring and if it's a common import `clojure-lsp` will suggest to add via code action 🎉 Check #lsp for more information
Some people have complained in #community-development about the frequency of some updates here for the same projects. I notice your last update was a week ago. I personally don't mind this, but for the people who do, I have made the #releases channel, to post smaller "in-between" updates. Just FYI. /cc @U45T93RA6
Oh, good point @U04V15CAJ, sorry for that I thought this channel was exactly for that, but it seems a #releases would fit better, thanks for the heads up, I'll post there from now 😄
Please don’t stop posting here as well now and then. For me personally, I prefer quite often. (Even once a week 😄 ) Releases of tools that make Clojure coding better should be celebrated!
Thank you @U0ETXRFEW! I'll probably try to merge features releases into a single release to avoid too many releases
I think we shouldn’t keep value from reaching our users. But, yeah, finding a good balance in what this or that target audience is interested in hearing about is tricky. We learn as we go, I guess.
Feel free to do what you want, I personally don't mind, just thought I should mention #releases as well, just in case you want to use it ;)
I sort of knew you did. But had to pretend to not understand, in order to make the joke. 😃
hahaha it's Doom Emacs @U7PBP4UVA, if you liked you can check my config on https://github.com/ericdallo/dotfiles
I don't know what is this doom-scrolling @U04V15CAJ :thinking_face:
Maybe it is this? https://www.wired.com/story/stop-doomscrolling/
hahaha got it, yeah it's supports @U04V15CAJ 😂
As a general rule of thumb, if you can still see an earlier announcement about your project in the scrollback on #announcements you should post it in #releases instead. Once your last announcement drops off the scrollback, feel free to post in #announcements again.
If you primarily maintain the version of your artifact in a pom.xml, I wrote a short GitHub action to respond to commit messages and perform the appropriate version bump against said pom. https://github.com/nnichols/maven-version-bump-action
As a general rule of thumb, if you can still see an earlier announcement about your project in the scrollback on #announcements you should post it in #releases instead. Once your last announcement drops off the scrollback, feel free to post in #announcements again.