Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove -q flag from git stash #1362

Open
stdedos opened this issue Dec 14, 2021 · 5 comments
Open

Remove -q flag from git stash #1362

stdedos opened this issue Dec 14, 2021 · 5 comments

Comments

@stdedos
Copy link

stdedos commented Dec 14, 2021

Problem description

Inadvertently dropping a stash in Sublime Merge, has no way of recovering it (that I know of)
All git stash commands are prefixed with -q; which forbids a savvy user to read the stash-hash from the outputs.

Preferred solution

Remove -q from the git stash commands.
Or just allow power users to do such overrides somehow.

Alternatives

A description of any alternative solutions or enhancements considered.

Screenshots

If applicable, add screenshots to help demonstrate the problem or proposed solution. This section may be omitted/removed.

@srbs
Copy link

srbs commented Dec 15, 2021

has no way of recovering it (that I know of)

As far as I know, Sublime Merge itself doesn't have a way to recover stash, however it is possible to recover: https://stackoverflow.com/a/91795.

@stdedos
Copy link
Author

stdedos commented Dec 15, 2021

Yeah - that is indeed a possibility.
If I would've lost something extremely important, that would've been indeed what I would be doing.
Thank you for leaving it here for the future readers.

However, I didn't loose something so significant so as to warrant that much trouble.
The alternative is:

➜  t git:(master) ✗  git stash
Saved working directory and index state WIP on master: d81bcd0 ...
➜  t git:(master) ✗  git stash pop
On branch master
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)

Untracked files:
  (use "git add <file>..." to include in what will be committed)

no changes added to commit (use "git add" and/or "git commit -a")
Dropped refs/stash@{0} (ce9d566eec29e6fd19988fc7d22bd72b872345e2)

Which clearly gives the ce9d566eec29e6fd19988fc7d22bd72b872345e2 hash mentioned in the page you added.

@stdedos
Copy link
Author

stdedos commented Jan 10, 2023

Idk what's more ridiculous. That git stash pop has no -q (whereas git stash drop has it), or that you don't improve "a very simple" and "non-destructive" feature request for more than a year now.

@BenjaminSchaaf @jskinner @wbond

@jfcherng
Copy link

jfcherng commented Jan 10, 2023

dpjohnst or srbs is likely the right person to tag btw.

@stdedos
Copy link
Author

stdedos commented Jan 10, 2023

Sorry @jfcherng, thank you 🙏

@srbs @dpjohnst

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants