Fork me on GitHub
#announcements
<
2021-01-07
>
nnichols01:01:20

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!

🔥 37
hyper-clap 9
👍 12
ericdallo01:01:17

Really cool! Does it checks for already open PRs by the GH action itself? Otherwise, each push it'll open a PR? 😅

nnichols01:01:53

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.

nnichols01:01:24

It ought to log a message that the PR exists and move on to the next stale dependency iirc

uochan02:01:48

Cool! I'll add a refence to antq's README (PR is also welcomed!) https://github.com/liquidz/antq#github-actions

ericdallo02:01:52

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

benedek14:01:15

that is nice

ericdallo12:01:45

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

metal 39
borkdude12:01:49

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

🙂 6
ericdallo12:01:17

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 😄

pez13:01:13

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!

ericdallo13:01:22

Thank you @U0ETXRFEW! I'll probably try to merge features releases into a single release to avoid too many releases

pez13:01:45

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.

😉 6
borkdude13:01:32

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 ;)

thanks 3
👍 3
orestis15:01:02

What editor is this?

pez15:01:30

All the editors! 😃

orestis15:01:04

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

pez15:01:53

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

ericdallo15:01:01

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

borkdude15:01:59

Does it support doom-scrolling?

ericdallo15:01:42

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

borkdude15:01:38

It is a new word I learned yesterday night

ericdallo15:01:05

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

seancorfield03:01:12

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.

👍 21
nnichols22:01:56

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

seancorfield03:01:12

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.

👍 21