git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Feature request: different exit codes for git stash depending on whether stash was created or not

From
IKIan Kemp <ian.kemp@gmail.com>
Date
Sep 27, 2019, 12:55 UTC
Message-ID
<CADZUK1cjvifbFYk9w6+vE95jgEBuwjoOi_1QfZHoPFBXuXHCCg@mail.gmail.com>
Hi,

Currently, git stash's exit code is 0 regardless of whether it performed a stash operation or not. Third parties invoking git stash are therefore unable to determine whether a stash was actually made or not.

It would be helpful if there were different exit codes for the case when a stash was created (working directory dirty) vs when a stash was not (working dir clean). git stash create suffers from the same issue.

There are various workarounds for this e.g. https://stackoverflow.com/a/34116244/70345 but they aren't particularly pretty or reliable, hence this request.

Regards, Ian

Next: Eric Sunshine
Message 1 of 3 in “Feature request: different exit codes for git stash depending on whether stash was created or not”
  1. Ian KempSep 27, 2019
  2. Eric SunshineSep 27, 2019
  3. brian m. carlsonSep 27, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.