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

Git: Add command for git stash drop #76195

Closed
leocb opened this issue Jun 26, 2019 · 3 comments
Closed

Git: Add command for git stash drop #76195

leocb opened this issue Jun 26, 2019 · 3 comments
Assignees
Labels
feature-request Request for new features or functionality git GIT issues good first issue Issues identified as good for first-time contributors help wanted Issues identified as good community contribution opportunities verification-needed Verification of issue is requested verified Verification succeeded
Milestone

Comments

@leocb
Copy link

leocb commented Jun 26, 2019

Issue Type: Bug

When poping a stash and there are merge conflicts between the stash and current code, even after the conflict is resolved, the pop'ed stash isn't dropped from the stash list.
The only way to drop a stash in vscode, AFAIK, is by successfully merging a stash, meaning that if a stash is no longer relevant (only conflicts, never merged), it can never be dropped from within vscode, only by a terminal command.

my suggestion is: when there are conflicts, let the user choose whether to resolve the conflicts or to just drop the stash.

VS Code version: Code 1.35.1 (c7d83e5, 2019-06-12T14:30:02.622Z)
OS version: Windows_NT x64 10.0.17763

@vscodebot vscodebot bot added the git GIT issues label Jun 26, 2019
@joaomoreno
Copy link
Member

When poping a stash and there are merge conflicts between the stash and current code, even after the conflict is resolved, the pop'ed stash isn't dropped from the stash list.

This is how git works. If you run git stash pop and the stash can't be popped, the stash will not be dropped. We will not deviate from Git's behavior here.

If you want to drop a stash, we can add a command for that. Would you like to submit a PR for that?

@joaomoreno joaomoreno changed the title Git Stash Pop with merge conflicts doesn't drop the stash Git: Add command for git stash drop Jun 27, 2019
@joaomoreno joaomoreno added feature-request Request for new features or functionality good first issue Issues identified as good for first-time contributors help wanted Issues identified as good community contribution opportunities labels Jun 27, 2019
@joaomoreno joaomoreno added this to the Backlog milestone Jun 27, 2019
@leocb
Copy link
Author

leocb commented Jun 28, 2019

I see, makes sense. Where should I place this stash drop feature? just in the command pallet or also in the git "more actions" (3 dots) menu?
If I manage to get some free time I will try to open a PR. But if anyone else wants to do it, please go ahead! :)

@drew212
Copy link
Contributor

drew212 commented Jun 29, 2019

I have a prototype working for this, want to check a few things and I'll submit a PR.

@joaomoreno joaomoreno modified the milestones: Backlog, October 2019 Oct 25, 2019
@joaomoreno joaomoreno added the verification-needed Verification of issue is requested label Oct 28, 2019
@alexr00 alexr00 added the verified Verification succeeded label Oct 29, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality git GIT issues good first issue Issues identified as good for first-time contributors help wanted Issues identified as good community contribution opportunities verification-needed Verification of issue is requested verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants