On failure of a pre-commit hook, run git stash pop
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
The issue reports that a failed pre-commit run leaves the stash unrestored, and the README is cited as documenting the stash step. Start by reading the README section on stashing and then reproduce with a pre-commit hook that fails, using a .overcommit.yml with a deliberately broken hook. Done means that after a failed run the stashed changes are restored, with a spec covering the failure path.
由索引模型根据 Issue 内容生成。
描述
I'm getting an error in the pre-commit hook run (I don't have any pre-commit hooks, but that's another issue). When the program finishes running, files have been stashed (as is mentioned in the README) but are not restored.
kenyon@Kenyons-MacBook-Pro ~b % git status
On branch BBS-3445-b
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: db/schema.rb
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: .git_hooks/post_commit/run_annotate_models.rb
modified: .overcommit.yml
kenyon@Kenyons-MacBook-Pro ~b % git commit
Unable to setup environment for pre-commit hook run:
STDOUT:
STDERR:Signature of configuration file has changed!
Run `overcommit --sign` once you've verified the configuration changes.
For more information, see https://github.com/sds/overcommit#security
kenyon@Kenyons-MacBook-Pro ~b % git status
On branch dev
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: file1.txt
kenyon@Kenyons-MacBook-Pro ~b % git stash pop
On branch dev
Changes to be committed:
(use "git restore --staged <file>..." to unstage)
modified: file1.txt
Changes not staged for commit:
(use "git add <file>..." to update what will be committed)
(use "git restore <file>..." to discard changes in working directory)
modified: file2.txt
modified: file3.txt
- 主要语言
- 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 半天 新手友好度 62/100
sds/overcommit#908 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 35/100
sds/overcommit#875 ·
维护者通常 1 天内回复
-
help wanted
难度 4/5 3-5 天 新手友好度 18/100
sds/overcommit#869 ·
维护者通常 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 天内回复