Use determinate-specific input names#157
Use determinate-specific input names#157heywoodlh wants to merge 1 commit intoDeterminateSystems:mainfrom
Conversation
📝 WalkthroughWalkthroughThis PR replaces the flake's top-level Nix and Nixpkgs inputs with Determinate-managed versions (determinate-nix and determinate-nixpkgs), updates the outputs function signature accordingly, and rewires all internal references to use the new inputs. Documentation is updated to reflect the new pattern. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Tip 🧪 Unit Test Generation v2 is now available!We have significantly improved our unit test generation capabilities. To enable: Add this to your reviews:
finishing_touches:
unit_tests:
enabled: trueTry it out by using the Have feedback? Share your thoughts on our Discord thread! Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
I watch my flake.lock pretty closely and don't like duplicate inputs. This renames generic inputs to something specific to Determinate -- since Determinate doesn't want users overriding
nixpkgs.Here's a snippet from my
flake.nixwhich removes duplicate inputs:Should probably not be merged until the same PR is approved and merged in nix-src.
Summary by CodeRabbit
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.