Requirements

🚀Requirements

Required Review

Verify the current branch, commit, tag, remotes, authentication, and protection rules before synchronization.

Commandcusty push

📦Category

Git Operations

🚀Quick Command

custy push [OPTIONS]

---

requirementsremotesauthentication

---

Overview

Push changes shared repository state. Verify the exact references and destinations before normal execution.

---

Push Requirements

📌Requirements

Reviewed HEAD

Required

Confirm the current branch and the exact HEAD commit that will be synchronized.

Reachable Main Remote

Required

At least one intended main remote must exist and be reachable.

Git Authentication

Required

Configure native SSH/Git authentication or Custy's optional protected external HTTPS fallback; never store a token value in config.toml.

Remote Permission

Required

The branch and account must satisfy remote protection and authorization rules.

Local Tag

Optional

A requested tag must exist locally and point to the intended commit.

Backup Remote

Optional

Configure an eligible backup destination only when backup synchronization is required.

---

Recommended Preflight

Terminal

bash

git status -sb
git log -1 --oneline --decorate
git remote -v
custy --dry-run push

---

⚠️Interactive remote fallback

When no main remote list reaches the workflow engine, the current implementation can ask whether it should use origin. Non-interactive environments should not depend on that prompt.

💡Container authentication

A container does not inherit the host credential-manager session. Use SSH through the normal Git environment, allow an approved interactive prompt, or configure the optional external fallback with custy configure credentials.