Pre-commit hooks can cause many of the commands to fail
- 主要言語
- Go
- スター
- 1.5k
- フォーク
- 70
- 平均マージ
- 1日 8時間
- マージ済み PR(30日)
- 7
説明
It would be nice if the commands that push supported a `--no-verify` flag. I've had to implement a local function like this to get around the pre-commit hooks that sometimes fail during push after a rebase.
```shell
# git stack --push without running hooks.
gs-push-quiet() {
git config core.hooksPath /dev/null
gh stack push
git config --unset core.hooksPath
}
```
Not all my colleagues use pre-commit, so sometimes a random change somewhere in the mono repo will block a push without `--no-verify`, even though all my commits are clean.
コントリビューションガイド
調査の方向性
Start at the gh stack push command and inspect how its command-line flags are defined and passed to Git. Check the other commands that push, then verify that --no-verify allows pushes to bypass pre-commit hooks without changing the normal behavior.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- git, github, go
- 領域
- cli, developer-experience
- issue の種類
- 機能追加
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 65/100