stash push -u: don't create empty stash

When introducing the stash push feature, and thus allowing users to pass in a pathspec to limit the files that would get stashed in df6bba0937 ("stash: teach 'push' (and 'create_stash') to honor pathspec", 2017-02-28), this developer missed one place where the pathspec should be passed in. Namely in the call to the 'untracked_files()' function in the 'no_changes()' function. This resulted in 'git stash push -u -- <non-existant>' creating an empty stash when there are untracked files in the repository other that don't match the pathspec. As 'git stash' never creates empty stashes, this behaviour is wrong and confusing for users. Instead it should just show a message "No local changes to save", and not create a stash. Luckily the 'untracked_files()' function already correctly respects pathspecs that are passed to it, so the fix is simply to pass the pathspec along to the function. Reported-by: Marc Strapetz <marc.strapetz@syntevo.com> Signed-off-by: Thomas Gummerer <t.gummerer@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Thomas Gummerer committed Mar 19, 2018 at 23:21 UTC d319bb18b1bd3e0b7269b44b9bae5db99dfbb7dd
2 files changed +7 -1
git-stash.sh
+1 -1
@@ -39,7 +39,7 @@ fi
39 no_changes () {
40 git diff-index --quiet --cached HEAD --ignore-submodules -- "$@" &&
41 git diff-files --quiet --ignore-submodules -- "$@" &&
42 - (test -z "$untracked" || test -z "$(untracked_files)")
42 + (test -z "$untracked" || test -z "$(untracked_files "$@")")
43 }
44
45 untracked_files () {
t/t3905-stash-include-untracked.sh
+6
@@ -274,4 +274,10 @@ test_expect_success 'stash -u -- <ignored> leaves ignored file alone' '
274 test_path_is_file ignored.d/bar
275 '
276
277 +test_expect_success 'stash -u -- <non-existant> shows no changes when there are none' '
278 + git stash push -u -- non-existant >actual &&
279 + echo "No local changes to save" >expect &&
280 + test_i18ncmp expect actual
281 +'
282 +
283 test_done