Examples

🚀Examples

Stable

Use cautious push patterns that expose actual resolved destinations before remote synchronization.

Commandcusty push

📦Category

Git Operations

🚀Quick Command

custy push [OPTIONS]

---

examplesdry-runremote safety

---

Overview

These examples use dry-run to verify the effective destination set before performing remote mutations.

⚠️Read every resolved destination

Cancel normal execution when the reported main or backup remote is not the intended destination.

---

Common Examples

📝Examples

Practical command examples.

Preview resolved destinations

Run validation and inspect which main remotes the engine resolves.

CLI

custy --dry-run push

---

💡Notes

Use this before every unfamiliar repository or configuration.

Push to exactly one remote

Override all configured groups and push only to upstream.

CLI

custy push --remote upstream

Push all configured groups

Push the de-duplicated main and eligible backup groups.

CLI

custy push --all-remote

Preview HEAD and a release tag

Show the intended HEAD and tag operations for each resolved remote.

CLI

custy --dry-run push --tag v1.4.0

Synchronize an eligible backup

Request backup synchronization in addition to normal main-remote processing.

CLI

custy push --sync-backup --tag v1.4.0

---

💡Notes

Non-critical branch rules can skip backup synchronization.

Run only after review

Push HEAD and the selected tag using the engine's actual resolved destinations.

CLI

custy push --tag v1.4.0

---

ℹ️Skip a tag deliberately

Use custy push --skip-tag to push HEAD without pushing a tag. In Release and Full profiles, the same option also prevents tag creation.