`gh stack push` with --no-verify flag
- Vorherrschende Sprache
- Go
- Sterne
- 1.5k
- Forks
- 70
- Ø Merge
- 1 T. 8 Std.
- Gemergte PRs (30 T.)
- 7
Beschreibung
## 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)
Beitragsleitfaden
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, go
- Bereich
- cli
- Issue-Typ
- Feature
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Ruhig
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 70/100