What did you do before the bug happened? (Steps to reproduce your issue)
$ git stash create "example message"
1e9b483d1f9477de5c99a708f4aa512ba
$ git stash store 1e9b483d1f9477de5c99a708f4aa512ba
$ git stash list
What did you expect to happen? (Expected behavior)
stash@{0}: example message
What happened instead? (Actual behavior)
stash@{0}: Created via "git stash store".
What's different between what you expected and what actually happened?
The documentation does not explain what the message "argument" is used for.
I would have expected that the message would be used by the store command.
Anything else you want to add:
If the message argument is not used at all, I would expect to
remove the argument, or
alternatively, that the documentation explains why the argument
exists and what it does/doesn't do.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.50.0
cpu: arm64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
libcurl: 8.7.1
zlib: 1.2.12
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
uname: Darwin 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:33
PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8122 arm64
compiler info: clang: 17.0.0 (clang-1700.0.13.3)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh
