Skip to content

fix(nix): consolidate flake inputs by adding missing follows declarations #1866

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Nov 21, 2025
Merged

fix(nix): consolidate flake inputs by adding missing follows declarations #1866

merged 2 commits into from
Nov 21, 2025

Conversation

@jfroche
Copy link
Collaborator

@jfroche jfroche commented Oct 27, 2025

Reduce duplication in flake.lock by adding follows declarations to

  • nix2container.inputs.nixpkgs → follows root nixpkgs
  • nix-editor.inputs.utils → follows root flake-utils
  • nix-editor.inputs.nixpkgs → follows root nixpkgs
  • rust-overlay.inputs.nixpkgs → follows root nixpkgs
  • nix-fast-build.inputs.flake-parts → follows root flake-parts
  • nix-fast-build.inputs.nixpkgs → follows root nixpkgs
  • nix-fast-build.inputs.treefmt-nix → follows root treefmt-nix

@jfroche
[jj-spr] initial version
4682f6a 
Created using jj-spr 1.3.6-beta.1
@jfroche
Rebase PR with latest change on flake.nix inputs
963fcc2 
Created using jj-spr 1.3.6-beta.1
@jfroche jfroche requested review from a team as code owners October 27, 2025 13:33
@samrose samrose added this pull request to the merge queue Nov 21, 2025
Merged via the queue into develop with commit afea09d Nov 21, 2025
24 of 25 checks passed
@samrose samrose deleted the jfroche/fixnix-consolidate-flake-inputs-by-adding-missing-follows-declarations branch November 21, 2025 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@samrose samrose samrose approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jfroche @samrose