push
Publish local commits to origin across your workspace.
Usage
git-wrangler push [options]Warning: Force-pushing rewrites remote history. Prefer
--force, which refuses to overwrite unexpected remote changes. Use--force-unsafeonly when you are certain no one else’s work will be lost.
Quick start
git-wrangler push
What it does
push publishes the current branch of each target repository to origin. Run review first to see which committed changes have not been pushed.
Use --force after an intentional history rewrite. It uses Git’s lease protection. The separate --force-unsafe option performs a raw force push and asks for confirmation first.
Options
| Option | Default | What it does |
|---|---|---|
--repo <path> |
Whole workspace | Push exactly one repository. |
--force |
Off | Force-push with lease protection. |
--force-unsafe |
Off | Force-push without lease protection after confirmation. |
--yes, -y |
Off | Skip the raw force-push confirmation. |
--guided |
Off | Choose options through prompts. |
--force and --force-unsafe cannot be used together.
More examples
# Push one repository
git-wrangler push --repo ./api
# Publish an intentional history rewrite with lease protection
git-wrangler push --force
Related commands
- Use
reviewbefore a normal push. - Read History rewriting safely before force-pushing rewritten commits.