diff options
| author | Jay Colson <jay@karma.net> | 2020-07-23 10:53:23 +0100 |
|---|---|---|
| committer | Sean Whitton <spwhitton@spwhitton.name> | 2020-07-24 15:19:02 -0700 |
| commit | ca8503d0bef294ad3057382235e8ca2899e3a74e (patch) | |
| tree | 90a31a93f4af555362c34439fbc8c8809c742292 /README.rst | |
| parent | 23cd13e4e2550b8af969da70c30a843343075022 (diff) | |
| download | git-remote-gcrypt-ca8503d0bef294ad3057382235e8ca2899e3a74e.tar.gz | |
git config to request abort if --force not passed
Default to emit a warning if the git config flag is not set.
Signed-off-by: Jay Colson <jay@karma.net>
Diffstat (limited to 'README.rst')
| -rw-r--r-- | README.rst | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -97,6 +97,18 @@ The following ``git-config(1)`` variables are supported: ``rsync://`` backend. If the flags are set to a specific remote, the global flags, if also set, will not be applied for that remote. +``remote.<name>.gcrypt-force-required`` + .. +``gcrypt.force-required`` + A known issue is that every git push effectively has a ``--force``. + + By default, git-remote-gcrypt will warn the user of this known issue + when a push is requested without the ``--force`` flag. + + If this flag is set to ``true``, git-remote-gcrypt will fail to push, + as a precaution, unless ``--force`` is passed to git or you prefix your + refspecs with a '+'. + Environment variables ===================== |