Skip to main content

FAQ

Frequently Asked Questions

Support Guide

Find answers about destination precedence, tags, backup remotes, Run equivalence, and dry-run behavior.

Commandcusty push

Category

Git Operations

Quick Command

custy push [OPTIONS]
FAQremotessupport

Overview​

These answers clarify which references the profile synchronizes and how destination precedence affects the effective remote set.

What Does Custy Push by Default?

The workflow pushes the current HEAD to resolved main remotes. It pushes a tag only when a tag is present in workflow state and tag pushing is not skipped.

Does `custy push` Create a Commit or Tag?

No. The push profile validates and synchronizes existing references. Create and review commits or tags first.

Can It Push to a Backup Remote?

Yes, when backup synchronization is enabled, an eligible backup remote resolves, and the current branch is not excluded by safety rules.

What Does `--remote` Override?

It selects exactly one destination and overrides --all-remote, tool.custy.git.push_to, and the configured remote groups.

How Does `custy run push` Differ?

Both forms select the registered push profile and propagate the same push options. Run profiles such as Dev, Release, and Full inherit the same selection precedence whenever their pipeline reaches the push step. The direct form disables hidden Rich rendering completely, while custy run push suspends its visible progress display during interactive authentication. Both forms give Git stable terminal ownership for username, PAT, and SSH prompts.

Does Dry-Run Contact the Remote?

Validation and remote resolution can still inspect repository and remote state. Its primary guarantee is that normal push mutations are replaced with reported intent; read the actual output for the current version.

Why Does Docker Ask for Credentials Again?

The container does not inherit the host credential-manager session. Use native SSH, answer an approved interactive prompt, or configure Custy's optional protected external fallback with custy configure credentials.

Why Does an Interactive Push Look Frozen?

Git is normally waiting for username and PAT input. Current Custy releases give manual Git authentication direct terminal ownership and print guidance before the prompt. Direct commands disable their otherwise hidden Rich renderer, and Run pipelines suspend visible progress until authentication finishes. If only custy push loses the prompt while custy run push works, rebuild or pull the current image. Do not submit two empty lines: GitHub can report Repository not found together with Authentication failed for missing access to a private repository.

What Is the Manual Docker Authentication Flow?

Run with -it and omit the managed credential mount or variable. Enter the provider username, then enter a PAT when Git asks for Password. The password field normally hides input. A disposable container does not retain these values and separate GitHub and GitLab remotes may prompt independently.

Does Custy Store My Token?

Never in project configuration. File mode stores it in an explicitly selected external protected file; environment mode reads the named runtime variable. Normal Git credentials and SSH remain owned by their native tools.

Can a Non-Interactive Push Wait for Input?

With the recommended fail_non_interactive = true, no. Git prompting is disabled when it cannot be answered, so the job fails with an actionable authentication error instead of hanging.