Repository navigation
test(auto-follow): siblings keep automatic follows next to an explicit one; document explicit follows - #153
Merged
Merged
Conversation
…ic follows; document explicit follows Adds a regression test for #151's fix: one explicitly configured nested follows must not drop the automatic follows of its siblings. Adds a short "Choosing a follow yourself" section to the auto-follow guide.
sini
force-pushed
the
fix/configured-follows-win
branch
from
October 25, 2026 04:45
39f3e8b to
4b8848f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #152, which fixed #151. Adds the two pieces #152 doesn't cover. No library change.
test unconfigured siblings keep automatic follows: one explicitly configured nested follows (foo.inputs.bar.follows = "quux") must not drop a sibling's automatic follows (foo.inputs.qux.follows = "baz"from the existingflake.nix).followswins, is written as configured and is excluded fromflake-edit follow, and that the other nested inputs keep their automatic follows.Validation
nix-unit --flake ./dev#tests(with--override-input flake-file path:..), on main 11f9c86 plus this commit: 450/450.nix run ./dev#fmt -- --ci: 0 files changed.