overcommit --run skips Git-quoted filenames with include filters
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with GitRepo.all_files in lib/overcommit/git_repo.rb around lines 138-143, which splits both git ls-files and git ls-files --deleted output on newlines. Reproduce with the scratch-repo steps in the issue, using a filename such as café.rb under core.quotePath=true, then check whether the TrailingWhitespace hook reports a failure. Done means NUL-delimited parsing for both lists, with regression specs covering Unicode, quoted, control-character, nested, deleted, untracked, empty-index and broken-symlink paths.
由索引模型根据 Issue 内容生成。
描述
Reproduced on current main 50f3e866bef75e3c3be7f92b47b1c45b6e7436ba (0.74.0), macOS 15.6.1, Ruby 4.0.7, Apple Git 2.50.1.
With Git's default core.quotePath=true, GitRepo.all_files returns the quoted/escaped output of git ls-files rather than actual paths. When a hook has an include pattern such as **/*.rb, those paths no longer match, and overcommit --run can report success without checking a tracked file.
Reproduction
Use a scratch repository, not an existing project:
mkdir overcommit-path-repro
cd overcommit-path-repro
git init
git config --local user.name 'Local Fixture'
git config --local user.email '[email protected]'
git config --local commit.gpgsign false
git config --local core.hooksPath /dev/null
git config --local core.quotePath true
git commit --allow-empty -m 'Initial fixture'
cat > .overcommit.yml <<'YAML'
PreCommit:
ALL:
enabled: false
TrailingWhitespace:
enabled: true
on_warn: fail
include:
- '**/*.rb'
YAML
overcommit --sign
printf 'puts "fixture" \n' > normal.rb
git add -- normal.rb
overcommit --run
# TrailingWhitespace FAILED; exit 65.
git mv -- normal.rb 'café.rb'
overcommit --run
# All pre-commit hooks passed; exit 0. The content is unchanged.
git config --local core.quotePath false
overcommit --run
# TrailingWhitespace FAILED again; exit 65.
The same false-success result occurs for filenames containing double quotes, tabs, or newlines. core.quotePath=false is a control for the Unicode case, not a general workaround for those other characters.
Scope
GitRepo.all_files in lib/overcommit/git_repo.rb:138-143 splits both git ls-files and git ls-files --deleted on newlines. Using NUL-delimited output for both lists would avoid interpreting Git's C-style filename quoting while retaining the deleted-file filtering added in #905.
This behavior predates #905; I am not reporting it as a regression from that PR. The older #220/#222 discussion concerned a repository root containing spaces and list_files. I reproduced this with the repository root itself containing a space, and ordinary space-containing basenames still work.
The regression cases should include live Unicode/quoted/control-character paths, a nested Unicode path, unstaged deletions, an empty index, untracked files, and a tracked broken symlink. The broken symlink must remain visible to the BrokenSymlinks hook.
Would a small all_files parsing fix with these tests be welcome? I would leave other Git helpers, command execution, and index-error handling out of this change.
- 主要语言
- Ruby
- 星标
- 4k
- 派生
- 288
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 18
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
sds/overcommit 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
sds/overcommit#909 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
sds/overcommit#847 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 35/100
sds/overcommit#875 ·
维护者通常 1 天内回复
-
help wanted
难度 4/5 3-5 天 新手友好度 18/100
sds/overcommit#869 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 25/100
sds/overcommit#856 ·
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
seek4science/seek#2784 ·
维护者通常 2 天内回复
-
Translation tutorial: snippet crashes on chunks export and misses simple { t } entries可能已有人在做 @Mahdi-Hasan 今天认领。 未关闭resource-documentation
难度 2/5 1-3 小时 新手友好度 76/100
TarteelAI/quranic-universal-library#1020 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
-
Records without the CRI logtag raise NoMethodError and are joined into the next record可能已有人在做 @nazarli-shabnam 今天认领。 未关闭bug help wanted
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 82/100
swombat/souls-house#842 ·
维护者通常 1 天内回复