Resolve relative paths after cd in compound commands#53
Merged
Conversation
When a compound command starts with `cd <literal>`, subsequent commands now resolve relative paths against the cd target directory rather than the original cwd. This allows config rules to match as users expect. Only handles literal paths (absolute, ~, relative). Dynamic targets (variables, command substitutions) are ignored and fall back to original cwd. Closes #52
orgoj
pushed a commit
to orgoj/Dippy
that referenced
this pull request
Jan 17, 2026
When `cd <literal> && ./foo` runs, resolve `./foo` against the cd target instead of the original cwd. This lets config rules match as users expect. Closes ldayton#52
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
1 participant
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.
When a compound command starts with
cd <literal>, subsequent commands now resolve relative paths against the cd target directory rather than the original cwd.Example:
Previously
./bin/toolresolved against the original cwd and didn't match. Now it resolves against~/projects/myappand matches the rule.Only handles literal paths (absolute,
~, relative). Dynamic targets (variables, command substitutions) fall back to original cwd.Closes #52