starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

How do I remove the right-click menu "open in Windows terminal"? #11223

New Issue
Open
opened 2026-01-31 02:41:54 +00:00 by claunia · 20 comments
claunia commented 2026-01-31 02:41:54 +00:00
Owner
Copy Link

Originally created by @rmwxxwmr on GitHub (Oct 30, 2020).

Is it possible to turn this feature on or off with an option?

Originally created by @rmwxxwmr on GitHub (Oct 30, 2020). Is it possible to turn this feature on or off with an option?
claunia added the Issue-TaskProduct-TerminalArea-ShellExtension labels 2026-01-31 02:41:54 +00:00
claunia commented 2026-01-31 02:41:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 30, 2020):

Ah no, we don't have a setting for that currently. Thanks for the request!

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

I'm also terribly worried that we can't control whether this is shown at runtime or not. Maybe in OpenTerminalHere::GetState? We'll probably want to wait till fOkToBeSlow, then load the settings, then check if it's enabled or not.

@zadjii-msft commented on GitHub (Oct 30, 2020): Ah no, we don't have a setting for that currently. Thanks for the request! I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? <hr> I'm also terribly worried that we can't control whether this is shown at runtime or not. Maybe in `OpenTerminalHere::GetState`? We'll probably want to wait till `fOkToBeSlow`, then load the settings, then check if it's enabled or not.
claunia commented 2026-01-31 02:41:55 +00:00
Author
Owner
Copy Link

@PathogenDavid commented on GitHub (Nov 12, 2020):

A workaround was posted in a similar issue:

Add a value named {9f156763-7844-4dc4-b2b1-901f640f5155} to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked and restart explorer. The menu item will be gone. (HKEY_CURRENT_USER works too.)

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

In my case I wanted to remove it because I'm still waiting on a handful of planned Terminal features before I really start using it, so until then it's just clutter.

IMO, removing shell extensions should always be an option. For every app that thinks it's being helpful adding its self to the Explorer context menu there's 10 more that are adding clutter.

That being said, it appears that Terminal is adding the shell extension via the appxmanifest, so I can imagine it's not as simple to provide an opt-out compared to traditional apps. (Maybe setting that HKCU\...\Blocked value is viable? Needing the restart is not the best UX though.)

@PathogenDavid commented on GitHub (Nov 12, 2020): [A workaround](https://github.com/microsoft/terminal/issues/7008#issuecomment-662621638) was posted in a similar issue: Add a value named [`{9f156763-7844-4dc4-b2b1-901f640f5155}`](https://github.com/microsoft/terminal/blob/ae550e0969595f062b15c2ff5cc33d4afe8ebc3f/src/cascadia/CascadiaPackage/Package.appxmanifest#L77) to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked` and restart explorer. The menu item will be gone. (`HKEY_CURRENT_USER` works too.) > I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? In my case I wanted to remove it because I'm still waiting on a handful of planned Terminal features before I really start using it, so until then it's just clutter. IMO, removing shell extensions should always be an option. For every app that thinks it's being helpful adding its self to the Explorer context menu there's 10 more that are adding clutter. That being said, it appears that Terminal is adding the shell extension via the [appxmanifest](https://github.com/microsoft/terminal/blob/ae550e0969595f062b15c2ff5cc33d4afe8ebc3f/src/cascadia/CascadiaPackage/Package.appxmanifest#L81-L94), so I can imagine it's not as simple to provide an opt-out compared to traditional apps. (Maybe setting that `HKCU\...\Blocked` value is viable? Needing the restart is not the best UX though.)
claunia commented 2026-01-31 02:41:55 +00:00
Author
Owner
Copy Link

@scx commented on GitHub (Nov 13, 2020):

@rmwxxwmr

Is it possible to turn this feature on or off with an option?

To disable this menu entry, just add the REG_SZ key in HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked. As the name, type {9F156763-7844-4DC4-B2B1-901F640F5155}. You don't have to enter any value, but I recommend to use something like WindowsTerminal or so. Then you have to restart Explorer.

Full guide:

  1. Run the following command in an elevated Command Prompt (e.g. Open Menu Start, search for cmd.exe, then right click on Command Prompt and choose Run as administrator:
REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked" /v "{9F156763-7844-4DC4-B2B1-901F640F5155}" /d "WindowsTerminal"
  1. Restart Explorer.

Alternatively, you can import this Windows Registry file:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked]
"{9F156763-7844-4DC4-B2B1-901F640F5155}"="WindowsTerminal"

Disable_WindowsTerminal.reg.txt

Don't forget to restart Explorer.

How did I come up with this?
Search Windows Registry for WindowsTerminal in HKCR (HKEY_CLASSES_ROOT).
Found:

  • HKEY_CLASSES_ROOT\PackagedCom\ClassIndex\{9F156763-7844-4DC4-B2B1-901F640F5155}\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe
  • HKEY_CLASSES_ROOT\PackagedCom\Package\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\Class\{9F156763-7844-4DC4-B2B1-901F640F5155}

You can use similar approach to disable other Microsoft shell extensions, e.g. Skype.

See also:
https://superuser.com/questions/1539765/how-to-remove-share-with-skype-from-the-windows-explorer-context-menu

@scx commented on GitHub (Nov 13, 2020): @rmwxxwmr > Is it possible to turn this feature on or off with an option? To disable this menu entry, just add the `REG_SZ` key in `HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked`. As the name, type `{9F156763-7844-4DC4-B2B1-901F640F5155}`. You don't have to enter any value, but I recommend to use something like `WindowsTerminal` or so. Then you have to restart Explorer. Full guide: 1. Run the following command in an [elevated Command Prompt](https://www.howtogeek.com/194041/how-to-open-the-command-prompt-as-administrator-in-windows-8.1/) (e.g. Open Menu Start, search for `cmd.exe`, then right click on `Command Prompt` and choose `Run as administrator`: ``` REG ADD "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked" /v "{9F156763-7844-4DC4-B2B1-901F640F5155}" /d "WindowsTerminal" ``` 2. [Restart Explorer](https://www.howtogeek.com/198815/use-this-secret-trick-to-close-and-restart-explorer.exe-in-windows/). Alternatively, you can import this Windows Registry [file](https://pastebin.com/raw/DQEF9FPM): ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Shell Extensions\Blocked] "{9F156763-7844-4DC4-B2B1-901F640F5155}"="WindowsTerminal" ``` [Disable_WindowsTerminal.reg.txt](https://github.com/microsoft/terminal/files/5537299/Disable_WindowsTerminal.reg.txt) Don't forget to restart Explorer. How did I come up with this? Search Windows Registry for `WindowsTerminal` in `HKCR` (`HKEY_CLASSES_ROOT`). Found: - `HKEY_CLASSES_ROOT\PackagedCom\ClassIndex\{9F156763-7844-4DC4-B2B1-901F640F5155}\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe` - `HKEY_CLASSES_ROOT\PackagedCom\Package\Microsoft.WindowsTerminal_1.3.2651.0_x64__8wekyb3d8bbwe\Class\{9F156763-7844-4DC4-B2B1-901F640F5155}` You can use similar approach to disable other Microsoft shell extensions, e.g. **Skype**. See also: https://superuser.com/questions/1539765/how-to-remove-share-with-skype-from-the-windows-explorer-context-menu
claunia commented 2026-01-31 02:41:55 +00:00
Author
Owner
Copy Link

@scx commented on GitHub (Nov 13, 2020):

@zadjii-msft

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

I cannot speak for others, but I would like to put all open shell here commands in one place. Moreover, I want to enable this for directory background as well.

directory_shell

directory_shell_admin

Why is Windows Terminal not good enough for me?

  • Slow startup: When I only need to execute one command or two, I prefer to run Command Prompt in Win32 Console.
  • Unable to detach tabs and move them between windows.
  • Unable to switch between tabs by mouse scroll (see: MATE Terminal).
@scx commented on GitHub (Nov 13, 2020): @zadjii-msft > I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? I cannot speak for others, but I would like to put all _open shell here_ commands in one place. Moreover, I want to enable this for directory background as well. ![directory_shell](https://user-images.githubusercontent.com/510369/99081979-de199100-25c3-11eb-83bd-8485180e1b20.png) ![directory_shell_admin](https://user-images.githubusercontent.com/510369/99081988-dfe35480-25c3-11eb-941a-d368deb28866.png) Why is Windows Terminal not good enough for me? - Slow startup: When I only need to execute one command or two, I prefer to run Command Prompt in Win32 Console. - Unable to detach tabs and move them between windows. - Unable to switch between tabs by mouse scroll (see: MATE Terminal).
claunia commented 2026-01-31 02:41:56 +00:00
Author
Owner
Copy Link

@oyealex commented on GitHub (Nov 27, 2020):

Your right click menu is so cool

@oyealex commented on GitHub (Nov 27, 2020): Your right click menu is so cool
claunia commented 2026-01-31 02:41:56 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 28, 2020):

Slow startup: When I only need to execute one command or two, I prefer to run Command Prompt in Win32 Console.

How much of this is attributable to the default profile being PowerShell? You .. know you can change it, right? 😄

@DHowett commented on GitHub (Nov 28, 2020): > Slow startup: When I only need to execute one command or two, I prefer to run Command Prompt in Win32 Console. How much of this is attributable to the default profile being PowerShell? You .. know you can change it, right? :smile:
claunia commented 2026-01-31 02:41:56 +00:00
Author
Owner
Copy Link

@Mystic8b commented on GitHub (Nov 28, 2020):

Change the letter "o" to a capital letter, please.
Open in Windows Terminal

@Mystic8b commented on GitHub (Nov 28, 2020): Change the letter "o" to a capital letter, please. `Open in Windows Terminal`
claunia commented 2026-01-31 02:41:57 +00:00
Author
Owner
Copy Link

@jleaves commented on GitHub (Dec 27, 2020):

I cannot speak for others, but I would like to put all open shell here commands in one place. Moreover, I want to enable this for directory background as well.

@scx How did you achieve this? It's soooo cool. I was planning to beautify my own context menu, but I was stuck on grouping commands into sub-menus. Would you mind sharing the relevant registry file for your right click menu?

@jleaves commented on GitHub (Dec 27, 2020): > I cannot speak for others, but I would like to put all _open shell here_ commands in one place. Moreover, I want to enable this for directory background as well. @scx How did you achieve this? It's soooo cool. I was planning to beautify my own context menu, but I was stuck on grouping commands into sub-menus. Would you mind sharing the relevant registry file for your right click menu?
claunia commented 2026-01-31 02:41:57 +00:00
Author
Owner
Copy Link

@kundan-panta commented on GitHub (Jan 31, 2021):

In addition to having the option to remove it, can we have another option to move it to the extended context menu (Shift+Right Click) instead, like the other shells?
My normal right click menu:
image
My extended context menu (Shift+Right Click):
image

@kundan-panta commented on GitHub (Jan 31, 2021): In addition to having the option to remove it, can we have another option to move it to the extended context menu (Shift+Right Click) instead, like the other shells? My normal right click menu: ![image](https://user-images.githubusercontent.com/16020775/106393153-78b78e00-63c3-11eb-8b60-a06546633386.png) My extended context menu (Shift+Right Click): ![image](https://user-images.githubusercontent.com/16020775/106393184-b9afa280-63c3-11eb-94f3-0df0a4bb303b.png)
claunia commented 2026-01-31 02:41:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 1, 2021):

@baigyanik That's being tracked in #6113

@zadjii-msft commented on GitHub (Feb 1, 2021): @baigyanik That's being tracked in #6113
claunia commented 2026-01-31 02:41:58 +00:00
Author
Owner
Copy Link

@kenijo commented on GitHub (Feb 1, 2021):

I cannot speak for others, but I would like to put all open shell here commands in one place. Moreover, I want to enable this for directory background as well.

@scx How did you achieve this? It's soooo cool. I was planning to beautify my own context menu, but I was stuck on grouping commands into sub-menus. Would you mind sharing the relevant registry file for your right click menu?

I think he is using FileMenuTools for this.
It is now a paid software but if you look around for v7.1, it was the last free version available I believe.

@kenijo commented on GitHub (Feb 1, 2021): > > > > I cannot speak for others, but I would like to put all _open shell here_ commands in one place. Moreover, I want to enable this for directory background as well. > > @scx How did you achieve this? It's soooo cool. I was planning to beautify my own context menu, but I was stuck on grouping commands into sub-menus. Would you mind sharing the relevant registry file for your right click menu? I think he is using FileMenuTools for this. It is now a paid software but if you look around for v7.1, it was the last free version available I believe.
claunia commented 2026-01-31 02:41:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 7, 2021):

Ah no, we don't have a setting for that currently. Thanks for the request!

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

image
Error happend.While want open windows terminal in a wsl2 folder.
This is why I want remove it from context menu.

@ghost commented on GitHub (Feb 7, 2021): > Ah no, we don't have a setting for that currently. Thanks for the request! > > I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? > ![image](https://user-images.githubusercontent.com/40977489/107144254-fefc4300-6974-11eb-96b8-da3ef34dc33d.png) Error happend.While want open windows terminal in a wsl2 folder. This is why I want remove it from context menu.
claunia commented 2026-01-31 02:41:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 8, 2021):

@arnoldcui What you're seeing is #8936, which was fixed in #8977 (though, not yet released)

@zadjii-msft commented on GitHub (Feb 8, 2021): @arnoldcui What you're seeing is #8936, which was fixed in #8977 (though, not yet released)
claunia commented 2026-01-31 02:41:59 +00:00
Author
Owner
Copy Link

@ilija1 commented on GitHub (Feb 17, 2021):

I'd also mention that in some versions of Windows (possibly Windows 10 included), having a lot of context menu items can have a noiticeable negative impact on overall OS performance and responsiveness. For that reason alone I tend to remove pretty much everything from context menus and disable pretty much all of the OS GUI animations and other fluff.

Some people prefer a very snappy, fluid, and minimalist OS experience. It feels bad to wait longer than say 15ms(or whatever the minimum time that humans are able to perceive is) for a context menu to pop up.

@ilija1 commented on GitHub (Feb 17, 2021): I'd also mention that in some versions of Windows (possibly Windows 10 included), having a lot of context menu items can have a noiticeable negative impact on overall OS performance and responsiveness. For that reason alone I tend to remove pretty much everything from context menus and disable pretty much all of the OS GUI animations and other fluff. Some people prefer a very snappy, fluid, and minimalist OS experience. It feels bad to wait longer than say 15ms(or whatever the minimum time that humans are able to perceive is) for a context menu to pop up.
claunia commented 2026-01-31 02:41:59 +00:00
Author
Owner
Copy Link

@konohomaru commented on GitHub (Feb 19, 2021):

@scx How to make Context Menu like yours?

@konohomaru commented on GitHub (Feb 19, 2021): @scx How to make Context Menu like yours?
claunia commented 2026-01-31 02:41:59 +00:00
Author
Owner
Copy Link

@Mystic8b commented on GitHub (Apr 20, 2021):

In recent updates, the type has changed to {02DB545A-3E20-46DE-83A5-1329B1E88B6B}.
Changed reg file of respected @scx
Remove Open in Windows Terminal.reg.txt

@Mystic8b commented on GitHub (Apr 20, 2021): In recent updates, the type has changed to {02DB545A-3E20-46DE-83A5-1329B1E88B6B}. Changed reg file of respected @scx [Remove Open in Windows Terminal.reg.txt](https://github.com/microsoft/terminal/files/6341911/Remove.Open.in.Windows.Terminal.reg.txt)
claunia commented 2026-01-31 02:41:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 20, 2021):

The CLSID changes based on which version of Terminal you have installed.

@DHowett commented on GitHub (Apr 20, 2021): The CLSID changes based on which version of Terminal you have installed.
claunia commented 2026-01-31 02:41:59 +00:00
Author
Owner
Copy Link

@Mystic8b commented on GitHub (Apr 20, 2021):

It is very uncomfortable. I really look forward to the opportunity to disable the item in the context menu from the terminal settings.

@Mystic8b commented on GitHub (Apr 20, 2021): It is very uncomfortable. I really look forward to the opportunity to disable the item in the context menu from the terminal settings.
claunia commented 2026-01-31 02:42:00 +00:00
Author
Owner
Copy Link

@levicki commented on GitHub (Nov 13, 2022):

@zadjii-msft

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

For me it is simple -- I don't need it, and the more context menu options are there, it is harder to find the one I want (especially when explorer starts randomly hiding and/or reordering some of them using some blackbox algorithm).

Furthermore, I want the Terminal app (and also any other app including say Visual Studio which is also adding a context menu item) to ask me on first run whether to register / enable context menu extension or not.

Rationale:
On my computer I should have the right to decide what is helpful for me, not developers, not project managers, not other users' feature requests.

Yet Microsoft keeps repeating this same user-hostile pattern over and over every time they add a new feature to any of their products -- instead of designing for feature discoverability by showing a dialog after update describing said new feature and offering 3 options (Enable, Disable, Change later in Settings), Microsoft forces the feature on everyone, and then only if enough people complain they grudgingly add an option to disable it.

Asking for user consent isn't rocket science. Not asking for it only shows disrespect (if not utmost contempt) that developers have for users.

@levicki commented on GitHub (Nov 13, 2022): @zadjii-msft > I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? For me it is simple -- I don't need it, and the more context menu options are there, it is harder to find the one I want (especially when explorer starts randomly hiding and/or reordering some of them using some blackbox algorithm). Furthermore, I want the Terminal app (and also any other app including say Visual Studio which is also adding a context menu item) to ask me on first run whether to register / enable context menu extension or not. **Rationale:** _On my computer I should have the right to decide what is helpful for me, not developers, not project managers, not other users' feature requests._ Yet Microsoft keeps repeating this same user-hostile pattern over and over every time they add a new feature to any of their products -- instead of designing for feature discoverability by showing a dialog after update describing said new feature and offering 3 options (Enable, Disable, Change later in Settings), Microsoft forces the feature on everyone, and then only if enough people complain they grudgingly add an option to disable it. Asking for user consent isn't rocket science. Not asking for it only shows disrespect (if not utmost contempt) that developers have for users.
claunia commented 2026-01-31 02:42:00 +00:00
Author
Owner
Copy Link

@alkaid616 commented on GitHub (Mar 2, 2025):

Ah no, we don't have a setting for that currently. Thanks for the request!

I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it?

I'm also terribly worried that we can't control whether this is shown at runtime or not. Maybe in ? We'll probably want to wait till , then load the settings, then check if it's enabled or not.OpenTerminalHere::GetState``fOkToBeSlow

When the context menu runs, it does not display "Open in Windows Terminal" in the desktop background and folder background because OpenTerminalHere::GetStatewas not called, I don't know why it wasn't called. This problem occurred after a period of use, and I can only use the system restore point for restoration.

@alkaid616 commented on GitHub (Mar 2, 2025): > Ah no, we don't have a setting for that currently. Thanks for the request! > > I'm curious as to why the context menu isn't working for you - is there a reason you want to be able to disable it? > > I'm also terribly worried that we can't control whether this is shown at runtime or not. Maybe in ? We'll probably want to wait till , then load the settings, then check if it's enabled or not.`OpenTerminalHere::GetState``fOkToBeSlow` When the context menu runs, it does not display "Open in Windows Terminal" in the desktop background and folder background because `OpenTerminalHere::GetState`was not called, I don't know why it wasn't called. This problem occurred after a period of use, and I can only use the system restore point for restoration.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-ShellExtension Issue-Task Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11223
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?