crit --range <base>..<head> still appears to initialize through working-tree change detection first. If current working tree has no changes, crit exits with:
Error: no changed files detected (after applying ignore patterns)
even when requested commit range has changed files.
Repro
In a repo where HEAD~1..HEAD has changes, but working tree is clean:
git status --short
# no output
git diff --name-status HEAD~1..HEAD
# M README.md
crit --range HEAD~1..HEAD --no-open
Expected
Crit opens range review for files changed in HEAD~1..HEAD.
Actual
Started crit daemon at http://localhost:<port> (PID <pid>)
Error: no changed files detected (after applying ignore patterns)
Version tested
v0.10.3
crit --range <base>..<head>still appears to initialize through working-tree change detection first. If current working tree has no changes, crit exits with:even when requested commit range has changed files.
Repro
In a repo where
HEAD~1..HEADhas changes, but working tree is clean:Expected
Crit opens range review for files changed in
HEAD~1..HEAD.Actual
Version tested
v0.10.3