-
-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
gomanagedocker: init at 1.4 #347300
gomanagedocker: init at 1.4 #347300
Conversation
9f108da
to
b1e4ed8
Compare
b1e4ed8
to
454dd14
Compare
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.
Excellent work; thank you for addressing this so quickly! Here are some optional recommendations for your continued maintenance of this derivation: (for future PRs)
- Add the
passthru.updateScript = nix-update-script { };
attribute, so @r-ryantm can reliably pick up updates to this package. The bot will create update pull requests for you, and as a maintainer, you'll be able to commit those automated updates into the repo by calling the @NixOS/nixpkgs-merge-bot. - Add automated testing for the package. A low-hanging fruit is the trivial
versioncheckhook
, which tests that you're actually building the right version. You may also want to build a TUI package testing suite likenano
's, or a full on NixOS virtual machine, as described in the manual.
Result of nixpkgs-review pr 347300
run on x86_64-linux 1
1 package built:
- gomanagedocker
f8a163b
to
4a466a7
Compare
If nix-update-script works without arguments, you might not need to add it to make the update work to work. |
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.