Patrick Hilhorst

I approve :+1: I was gonna write a separate nix-linter LSP plugin, but integrating it here seems like a good idea.

https://github.com/nix-community/nixpkgs-update-github-releases/issues/9 is done.

I'm very much in favour of using some OSM variant.

Not sure I like this. There currently is no seperator in lists, and this would add that. I'd propose a `list select` instead, something like: ``` attrs.[a b c] ```...

> > Lists in especially NixOS modules are fundamentally flawed in that they depend on the ordering of modules, which is very unintuitive and can cause weird problems. > >...

Hmm I wasn't aware how significant the order was for buildInputs...

Still relevant

Good idea, might take a stab at this later. @davidak: the action could live in a separate repo, so I don't see how.

@davidak Say we migrate to say... Gitlab. In that case, we could simply update the action to open a PR to the new Gitlab repo instead of the old Github...

I noticed some packages actually don't always release on Github, so we should probably also check in the script (nixpkgs-update-github-releases) if it is newer.