Re: Bug: "git stash create" ignores "message" argument

Hi all,

Thank you for taking the time to look at this issue.

I don’t have a specific use case for these commands yet. I was simply trying to learn more about Git and naturally turned to the documentation. However, it didn’t provide many answers for these commands. I understood that a use case is to create a commit object and then store it in the stash reference. And as I kept experimenting, I noticed I could pass a message to the create command, but it wasn’t clear what the command does with it.

From the perspective of someone trying to become more proficient with Git, the documentation didn’t help in this case. I wasn’t sure if this was a bug in the code, a documentation issue, or both. After reading your answers, this seems to be mostly a documentation issue: if the command and options are there, they should provide enough clarity to understand their basic purpose and functionality, right? It also makes me wonder if these commands aren’t commonly used because their use case and concrete usage steps are unclear (chicken-egg problem?)

For example, my understanding was that commit objects created with git stash create could only be used to add them to the stash. But your comments have let me see that this is incorrect, and that these commit objects can actually be used to create new branches, perform a cherry-pick, and so on. tbh, I find it odd that a command of the "stash" family can create a commit object that can be used for other things. I can understand that this is legacy and can live with that, but it’d still be great to have it documented so people can learn about these commands.

Looking forward to hearing more from your insights.

Cheers, José Miguel