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

SCM should close associated editors when associated resources are committed or discarded #135276

Closed
bpasero opened this issue Oct 18, 2021 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality papercut 🩸 A particularly annoying issue impacting someone on the team scm General SCM compound issues
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented Oct 18, 2021

One of my biggest SCM papercut issues is that the diff editors I had opened when reviewing an outgoing change remain open even after I committed the changes or discarded them. That makes my quick open history picker get polluted with diff editors that are no longer valid.

Would be great if any editor that was opened from a change get's discarded when done.

@bpasero bpasero added scm General SCM compound issues papercut 🩸 A particularly annoying issue impacting someone on the team labels Oct 18, 2021
@lszomoru lszomoru added the feature-request Request for new features or functionality label Oct 25, 2021
@lszomoru lszomoru modified the milestones: November 2021, Backlog Nov 2, 2021
@bpasero
Copy link
Member Author

bpasero commented Dec 27, 2021

/duplicate #18651

@omidantilong
Copy link

omidantilong commented Dec 29, 2021

I left a comment in the other thread about this. I love VS Code but this bugs me a lot, every day. At its most basic surely this could be accomplished with a command palette action to close any tabs with (Working Tree) in their title. I don't mind doing it once. It's the messing around with X number of tabs in no coherent order after reviewing big changes that really annoys me. A one shot "dumb" command to kill them all would save so much time.

Edit to add... if I'm overlooking something, I apologise in advance! :)

@bpasero bpasero closed this as completed Jan 31, 2022
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 31, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Mar 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) feature-request Request for new features or functionality papercut 🩸 A particularly annoying issue impacting someone on the team scm General SCM compound issues
Projects
None yet
Development

No branches or pull requests

3 participants