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.

Sign up for GitHub

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

Jump to bottom

Prevent Terminal from Auto Upgrading When Terminal is Open and In Use #13620

Closed
AathifMahir opened this issue Jul 28, 2022 · 3 comments
Closed

Prevent Terminal from Auto Upgrading When Terminal is Open and In Use #13620

AathifMahir opened this issue Jul 28, 2022 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@AathifMahir
Copy link

Description of the new feature/enhancement

Windows Terminal Updates Itself through Microsoft Store or Other Update Mechanisms when the Terminal is Open or In Use, This Could Make the users to lose Operation that were currently running in Terminal

Proposed technical implementation details (optional)

Implement a Feature that Detects, If the Terminal is Open and In Use, If that's true pause the Auto Update Until the Windows Terminal Gets Closed and Not in Use
@AathifMahir AathifMahir added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 28, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 28, 2022
@j4james
Copy link
Collaborator

j4james commented Jul 28, 2022

See issue #3915.

@zadjii-msft
Copy link
Member

Yep. Also see #6726 (comment) - the Store team is actively working on rolling this out.

/dup #3915
/dup #6726

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2022
@ghost
Copy link

ghost commented Jul 28, 2022

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Jul 28, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jul 28, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@j4james @AathifMahir @zadjii-msft