Network timeout error during Git push in GitKraken – retry behavior undecided

Network timeout error during Git push in GitKraken

The goal is to determine whether GitKraken should automatically retry a push after a transient network timeout without prompting the user.

Current behavior lets the user configure a retry count in Preferences → Git → General, leaving the decision to manual confirmation after each failure. This raises uncertainty about the trade‑off between convenience and the risk of duplicate writes if the remote already accepted part of the push.

Specific questions:

• Should GitKraken enable automatic retries by default for network‑timeout errors?
• What safety checks (e.g., remote ref status) must be performed before an automatic retry to avoid duplicate objects?
• How should the retry count setting interact with an automatic‑retry mode?