Clojurians Log v2

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 @nichols1991!

I'll try to add it to clojure-lsp later, thanks!

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 @vemv

Oh, good point @borkdude, 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 @pez! 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 ;)

What editor is this?

All the editors! 😃

Haha sorry I meant on the gif. Can’t tell if it’s a fancy vim or Emacs 😎

I sort of knew you did. But had to pretend to not understand, in order to make the joke. 😃

hahaha it's Doom Emacs @orestis, if you liked you can check my config on https://github.com/ericdallo/dotfiles

Does it support doom-scrolling?

I don't know what is this doom-scrolling @borkdude :thinking_face:

It is a new word I learned yesterday night

Maybe it is this? https://www.wired.com/story/stop-doomscrolling/

hahaha got it, yeah it's supports @borkdude 😂

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