Skip to content
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

Get treefmt-nix using a FOD instead of as a flake input #89

Merged
merged 1 commit into from
Feb 22, 2025

Conversation

kuruczgy
Copy link
Owner

Since flake inputs are propagated to downstream users of our flakes, having treefmt-nix in there is somewhat inconvenient, since it's only used for development.

You can verify based on the diff that the rev and hash of the treefmt-nix version used stayed the same.

Fixes #65

Since flake inputs are propagated to downstream users of our flakes,
having treefmt-nix in there is somewhat inconvenient, since it's only
used for development.

You can verify based on the diff that the rev and hash of the
treefmt-nix version used stayed the same.
@kuruczgy kuruczgy force-pushed the pr/remove-treefmt-nix-flake-input branch from e87fe6d to 0d3c011 Compare February 22, 2025 12:04
@kuruczgy kuruczgy merged commit 0d3c011 into main Feb 22, 2025
2 checks passed
@kuruczgy kuruczgy deleted the pr/remove-treefmt-nix-flake-input branch February 22, 2025 12:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Figure out if we can avoid having downstream flakes add treefmt-nix to their lockfiles
1 participant