git prompt: resilient check for git stash #6876
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charego
force-pushed
the
git-prompt-stash
branch
from
96f6751
to
b4a6cb7
Compare
|
The informative git prompt checks for |
Yeah let's do that. |
When you run "git gc": - .git/refs/stash is deleted - .git/logs/refs/stash is kept intact
charego
force-pushed
the
git-prompt-stash
branch
from
b4a6cb7
to
3f65d75
Compare
|
@krobelus Done, and updated commit message. |
|
Neat, thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
The refs/stash file is deleted by "git gc". The prompt won't display
stash information until another "git stash" command is run.
Using "git rev-parse stash" seems more resilient.
Based the choice on "git stash" test cases:
https://github.com/git/git/blob/master/t/t3903-stash.sh
There is still one edge case that I know of:
this will report that there are stashes