TortoiseGit Push to Public Remote Without Confirmation Prompt

TortoiseGit Push to Public Remote Without Confirmation Prompt

The goal is to prevent TortoiseGit from pushing local commits to a publicly accessible remote without an explicit warning or confirmation. The Push dialog sends commits to the remote URL stored in .git/config, and TortoiseGit does not classify remotes as public or private.

No TortoiseGit setting appears to warn or block before pushing to a new remote that may expose repository contents publicly. Access control depends on the remote host and supplied credentials, and behavior may differ between TortoiseGit versions and between PuTTY-based and OpenSSH-based SSH configurations.

Is there a TortoiseGit option to require confirmation before pushing to a remote that may be publicly accessible? If no such option exists, can a client-side hook enforce this boundary, and does enforcement remain consistent across recent TortoiseGit releases?