Skip to content

fix(apply): correct condition for setting --impure with commit messages#102

Merged
water-sucks merged 1 commit intonix-community:mainfrom
water-sucks:use-correct-cond-for-git-commit-msgs
Aug 18, 2025
Merged

fix(apply): correct condition for setting --impure with commit messages#102
water-sucks merged 1 commit intonix-community:mainfrom
water-sucks:use-correct-cond-for-git-commit-msgs

Conversation

@water-sucks
Copy link
Copy Markdown
Collaborator

Oops. Turns out I was only setting --impure if the generation tag was EMPTY! That's moronic, and I'm surprised I haven't caught this earlier during testing :{

@water-sucks water-sucks force-pushed the use-correct-cond-for-git-commit-msgs branch from 0f57343 to 6bfff64 Compare August 18, 2025 13:44
@water-sucks water-sucks changed the title fiz(apply): correct condition for setting --impure with commit messages fix(apply): correct condition for setting --impure with commit messages Aug 18, 2025
@water-sucks water-sucks merged commit 02a4047 into nix-community:main Aug 18, 2025
1 check passed
@water-sucks water-sucks deleted the use-correct-cond-for-git-commit-msgs branch August 18, 2025 15:26
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.

1 participant