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

[PR #2593] [MERGED] doc: move cascadia specs and rename them to spec format #25001

New Issue
Open
opened 2026-01-31 09:06:39 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:06:39 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/2593
Author: @DHowett-MSFT
Created: 8/29/2019
Status: ✅ Merged
Merged: 8/30/2019
Merged by: @DHowett-MSFT

Base: master ← Head: dev/duhowett/housecleaning

📝 Commits (2)

  • db05c87 doc: move cascadia specs and rename them to spec format
  • 30b3b70 More YFM

📊 Changes

3 files changed (+3 additions, -1 deletions)

View changed files

📝 doc/specs/#1142 - Keybinding Arguments.md (+0 -0)
📝 doc/specs/#532 - Panes and Split Windows.md (+3 -1)
📝 doc/specs/#754 - Cascading Default Settings.md (+0 -0)

📄 Description

This pull request moves the cascadia specs from /doc/cascadia to /doc/specs and renames them to follow the spec format.

I may push additional changes to add yaml front matter to the specs that are missing it.

Query: should cascadia specs be in their own folder? Is that a hollow distinction?

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/2593 **Author:** [@DHowett-MSFT](https://github.com/DHowett-MSFT) **Created:** 8/29/2019 **Status:** ✅ Merged **Merged:** 8/30/2019 **Merged by:** [@DHowett-MSFT](https://github.com/DHowett-MSFT) **Base:** `master` ← **Head:** `dev/duhowett/housecleaning` --- ### 📝 Commits (2) - [`db05c87`](https://github.com/microsoft/terminal/commit/db05c878ada954d89b83d9f66537256eb79dff43) doc: move cascadia specs and rename them to spec format - [`30b3b70`](https://github.com/microsoft/terminal/commit/30b3b707d39c8e837b98a8bbea3cbd7a78aeaceb) More YFM ### 📊 Changes **3 files changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `doc/specs/#1142 - Keybinding Arguments.md` (+0 -0) 📝 `doc/specs/#532 - Panes and Split Windows.md` (+3 -1) 📝 `doc/specs/#754 - Cascading Default Settings.md` (+0 -0) </details> ### 📄 Description This pull request moves the cascadia specs from `/doc/cascadia` to `/doc/specs` and renames them to follow the spec format. I may push additional changes to add yaml front matter to the specs that are missing it. Query: should cascadia specs be in their own folder? Is that a hollow distinction? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:06:39 +00:00
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 pull-request
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#25001
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?