From: Scott Johnson <jaywir3@gmail.com>
To: git@vger.kernel.org
Subject: Would a config var for --force-with-lease be useful?
Date: Fri, 24 Aug 2018 11:39:27 -0500 [thread overview]
Message-ID: <CAEFop40OJ5MRwM8zxE44yB0f2Fxw9YsUdM1e-H=Nn9e=sAGJ=w@mail.gmail.com> (raw)
Hello Everyone:
I'm considering writing a patch that adds a configuration variable
that will allow the user to default the command:
git push --force
to:
git push --force-with-lease
As discussed here:
https://stackoverflow.com/questions/30542491/push-force-with-lease-by-default
Now, I understand that there are downsides to having this enabled,
namely that a user who has this enabled might forget that they have it
enabled, and, as such, on a machine that _doesn't_ have it enabled (of
which they are unfamiliar) might then run the more consequential
command "git push --force", but my thinking is that adding this as a
feature to the git codebase as an _optional_ (i.e. not enabled by
default) configuration variable would then save some of us who use a
"rebase-then-force-push for pull request" workflow some time and
headaches.
Of course, I don't want to submit a patch if this is a feature that
isn't likely to be accepted, so I wanted to get some thoughts from the
mailing list regarding this idea.
Thank you,
~Scott Johnson
next reply other threads:[~2018-08-24 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 16:39 Scott Johnson [this message]
2018-08-25 13:34 ` Would a config var for --force-with-lease be useful? Constantin Weißer
2018-08-27 21:21 ` Johannes Schindelin
2018-08-28 9:59 ` Phillip Wood
2018-08-27 19:24 ` Junio C Hamano
2018-08-27 19:40 ` Ævar Arnfjörð Bjarmason
2018-08-27 20:09 ` Junio C Hamano
2018-08-27 20:44 ` Ævar Arnfjörð Bjarmason
2018-08-27 22:29 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEFop40OJ5MRwM8zxE44yB0f2Fxw9YsUdM1e-H=Nn9e=sAGJ=w@mail.gmail.com' \
--to=jaywir3@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).