Workflow

🚀Push Workflow

Stable

Follow validation, remote resolution, HEAD synchronization, optional tag publication, and backup behavior.

Commandcusty push

📦Category

Git Operations

🚀Quick Command

custy push [OPTIONS]

---

workflowremotessynchronization

---

Overview

The profile validates repository state before resolving and processing each eligible destination. A standalone custy push or custy run push does not initialize a release workflow, calculate a new version, or ask for release confirmation.

---

Workflow Timeline

🕒Push Profile

1

Validate repository

Run repository and pre-push validation.

completed

2

Resolve selection precedence

Apply explicit --remote, all_remote, then push_to to select the effective groups.

completed

3

Apply backup safety

Remove backup destinations when the current non-critical branch is not eligible.

optional

4

Resolve authentication

Use native Git or SSH first, then an enabled external token source for an eligible container HTTPS push.

optional

5

Push HEAD

Push the current HEAD to each resolved main and backup remote.

completed

6

Push tag

Push the selected tag when one is available and tag push is not skipped.

optional

---

ℹ️Fail-fast behavior

A failed main push raises an error and stops normal progress. Check the reported remote, authentication, network, branch protection, and rejected history before retrying.

When an interactive terminal is unavailable, the recommended credential policy prevents Git from waiting indefinitely for input. Configure an external file or environment token before running a non-interactive container push.

---

Retry Safety

After a failure, inspect the remote response and determine which earlier destinations already succeeded. Do not assume every remote remains unchanged.