summaryrefslogtreecommitdiffstats
path: root/contrib/persistent-https
diff options
context:
space:
mode:
authorPatrick Steinhardt <ps@pks.im>2026-02-16 07:45:44 +0100
committerJunio C Hamano <gitster@pobox.com>2026-02-17 08:37:51 -0800
commit76a3f28243ebb0be492f30210f2426a9f511f920 (patch)
treee37b630617848faa880746f6c511fd7b0f8f2b3a /contrib/persistent-https
parent453e7b744aef0d9dab62dac6ab030bb643a2e117 (diff)
downloadgit-76a3f28243ebb0be492f30210f2426a9f511f920.tar.gz
git-76a3f28243ebb0be492f30210f2426a9f511f920.zip
builtin/history: perform revwalk checks before asking for user input
When setting up the revision walk in git-history(1) we also perform some verifications whether the request actually looks sane. Unfortunately, these verifications come _after_ we have already asked the user for the commit message of the commit that is to be rewritten. So in case any of the verifications fails, the user will have lost their modifications. Extract the function to set up the revision walk and call it before we ask for user input to fix this. Adapt one of the tests that is expected to fail because of this check to use false(1) as editor. If the editor had been executed by Git, it would fail with the error message "Aborting commit as launching the editor failed." Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/persistent-https')
0 files changed, 0 insertions, 0 deletions