`gh stack push` with --no-verify flag
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 70
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
## Summary
When running the `gh stack push` command, there is no way to bypass the `git` pre-push webhooks on branches. This prevents skipping e.g long running tests when pushing the branch to remote.
## Proposal
Enable running the `gh stack push` command with the `--no-verify` flag similar to the `git push` -`-no-verify` flag [git flag Link](https://git-scm.com/docs/git-push#Documentation/git-push.txt---no-verify)
Contributor guide
Research direction
Start at the `gh stack push` command entry point and inspect how it invokes `git push` and defines command flags. Add support for `--no-verify` so the push can bypass Git pre-push hooks, then verify that normal pushes still run hooks and the flag is forwarded correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100