Error given when a push fails due to hook failure is not useful
还没有人认领这个 Issue。
评估
调研方向
Reproduce the failure with a pre-push hook using gh stack sync, gh stack push, and gh stack submit, then inspect the push error handling for those commands. Preserve and surface the hook's useful error output instead of only reporting that refs failed; verify the resulting messages against a regular git push.
由索引模型根据 Issue 内容生成。
描述
I have a pre-push hook setup on my local repos.
When I try gh stack sync it results in this:
Pushing 3 branches to origin...
⚠ Push failed — branches may need force push after rebase
When I try gh stack push it results in this:
Pushing 3 branches to origin...
✗ failed to push: failed to run git: error: failed to push some refs to 'github.com:<my_repo>'
When I try gh stack submit it results in this:
Pushing to origin...
✗ failed to push <my_branch>: failed to run git: error: failed to push some refs to 'github.com:<my_repo>'
Eventually I was able to guess it was my pre-push hook and tried a regular push and it told me what the error was immediately.
- 主要语言
- Go
- 星标
- 1.5k
- 派生
- 73
- 平均合并
- 1 天 8 小时
- 30 天内合并 PR
- 7
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
github/gh-stack 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
-
难度 1/5 1 小时以内 新手友好度 92/100
-
feature request topic: cli - general
难度 2/5 1-3 小时 新手友好度 68/100
-
feature request topic: auto-merge
难度 2/5 1-3 小时 新手友好度 68/100
-
bug topic: docs
难度 1/5 1 小时以内 新手友好度 68/100
相似的 Issue
-
textual definition
难度 1/5 1 小时以内 新手友好度 90/100
geneontology/go-ontology#32653 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
-
needs design
难度 2/5 1-3 小时 新手友好度 75/100
-
Priority/High ready-for-agent Severity/Major Type/Bug
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 70/100