-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated Nixpkgs update #14
Conversation
Things I wish:
I wish this about With nixpkgs in particular, there's a lot of metadata to mine that would make this a gorgeous "hell yes" or "hell no" moment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's unleash the CI at it.
Oh there's this problem where PRs from workflows don't trigger workflows themselves 🤔 |
Hrm. That's not copacetic. I can kind of imagine the reasoning. It's really easy to make something that's an accidental fork-bomb of GitHub resources. |
Workarounds are listed here. I think using a separate machine account is probably the best one in our case. |
Should we setup dependabot also to update cargo dependencies? |
Dependabot feels a bit too GitHub-centric, how about just adding a |
cdf3702
to
6172cb8
Compare
This guy is wedged. We'll unwedge something else. |
Improves upon the automated update PRs introduced in #12 to resolve issues brought up in the first automated PR #14. * Give more information about the updates, not much, but at least the output of npins update * Update all npins sources, not just Nixpkgs. * Run `cargo update` * Make it trigger CI by using an unprivileged separate machine account (welcome, @infinixbot!) * Set committer and author of the commits to the machine account
Update the pinned Nixpkgs automatically