Problem
ez push always creates or updates a PR. Sometimes users want to push a branch to the remote without creating a PR — for backup, CI, sharing with a collaborator, or because they are not ready for review.
Current behavior
ez push = git push + gh pr create/edit — always touches PRsez submit = push whole chain + create/update all PRs- No way to push without PR side effects
Proposed solution
ez push --no-pr — push the current branch to the remote without creating/updating a PRez submit --no-pr — push the whole chain without touching PRs- When
--no-pr branches are later pushed without the flag, PRs are created as usual
Alternatives considered
- Users could use
git push directly, but that bypasses ez's remote tracking and branch naming
- A separate
ez backup command, but that adds unnecessary surface area
Use cases
- Work-in-progress backup to remote
- Sharing branch with collaborator before PR
- CI builds triggered by branch push, not PR
- Incremental pushes during development
Problem
ez pushalways creates or updates a PR. Sometimes users want to push a branch to the remote without creating a PR — for backup, CI, sharing with a collaborator, or because they are not ready for review.Current behavior
ez push=git push+gh pr create/edit— always touches PRsez submit= push whole chain + create/update all PRsProposed solution
ez push --no-pr— push the current branch to the remote without creating/updating a PRez submit --no-pr— push the whole chain without touching PRs--no-prbranches are later pushed without the flag, PRs are created as usualAlternatives considered
git pushdirectly, but that bypasses ez's remote tracking and branch namingez backupcommand, but that adds unnecessary surface areaUse cases