You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One feature that I like a lot about niv-updater-actions is that it includes the relevant bits from the upstream git changelog in the PR description (and, somewhat related, it keeps updating the same PR until it can get merged, so if merging takes longer it will not create many PRs).
(It munges the changelog so that commit and PR references point to the right repo, and that they don’t spam upstream PRs with “this PR has been mentioned”.)
Would this be a useful feature for update-flake-lock as well?
Rather than RegEx, a better way would be to hook into nix flake update directly. Could it produce an AST? Failing that, parsing flake.lock (since it's just JSON) could work.
detsys-pr-bot
pushed a commit
to detsys-pr-bot/update-flake-lock
that referenced
this issue
Oct 10, 2024
This action looks like it’s the natural replacement for https://github.com/knl/niv-updater-action when moving from niv to flakes.
One feature that I like a lot about niv-updater-actions is that it includes the relevant bits from the upstream git changelog in the PR description (and, somewhat related, it keeps updating the same PR until it can get merged, so if merging takes longer it will not create many PRs).
(It munges the changelog so that commit and PR references point to the right repo, and that they don’t spam upstream PRs with “this PR has been mentioned”.)
Would this be a useful feature for
update-flake-lock
as well?If so, a possible (optional) extension would be to only lists those upstream commits that actually changed the derivation of the current flake’s outputs – useful when upstream has lots of unrelated changes, as
nixpkgs
tends to do, as outlined in https://discourse.nixos.org/t/bumping-flake-inputs-bisecting-input-repo-for-relevant-changelog-entries/25619/7?u=nomeata.The text was updated successfully, but these errors were encountered: