From: Pushkar Singh <pushkarkumarsingh1970@gmail•com>
To: pushkarkumarsingh1970@gmail•com
Cc: git@vger•kernel.org, gitster@pobox•com, peff@peff•net, ps@pks•im
Subject: [PATCH v2] stash: add coverage for show --include-untracked
Date: Sat, 16 May 2026 18:33:48 +0000 [thread overview]
Message-ID: <20260516183347.4323-2-pushkarkumarsingh1970@gmail.com> (raw)
In-Reply-To: <20260505103332.43702-2-pushkarkumarsingh1970@gmail.com>
Add a test for 'git stash show --include-untracked' to
cover the case where untracked files saved in the stash
are included in the output.
While stash creation and restoration of untracked files
are already tested, there is currently no explicit test
covering the output behavior of 'stash show
--include-untracked'.
Signed-off-by: Pushkar Singh <pushkarkumarsingh1970@gmail•com>
---
Changes in v2:
- Clarify in the commit message that the patch fills a gap
in existing test coverage for 'stash show
--include-untracked'
t/t3903-stash.sh | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/t/t3903-stash.sh b/t/t3903-stash.sh
index 70879941c2..d4867536b9 100755
--- a/t/t3903-stash.sh
+++ b/t/t3903-stash.sh
@@ -1790,4 +1790,21 @@ test_expect_success 'stash.index=false overridden by --index' '
test_cmp expect file
'
+test_expect_success 'stash show --include-untracked includes untracked files' '
+ git reset --hard &&
+
+ echo tracked >tracked &&
+ git add tracked &&
+ git commit -m "base" &&
+
+ echo change >>tracked &&
+ echo untracked >untracked &&
+
+ git stash push --include-untracked &&
+ test_path_is_missing untracked &&
+
+ git stash show --include-untracked >actual &&
+ test_grep "untracked" actual
+'
+
test_done
--
2.53.0.582.gca1db8a0f7
prev parent reply other threads:[~2026-05-16 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 10:33 [PATCH] stash: test show --include-untracked includes untracked files Pushkar Singh
2026-05-16 18:33 ` Pushkar Singh [this message]
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=20260516183347.4323-2-pushkarkumarsingh1970@gmail.com \
--to=pushkarkumarsingh1970@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=ps@pks$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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