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

Feature Request: Make Release Notes easily available possibly using new About section #1612

New Issue
Open
opened 2026-01-30 22:32:03 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:32:03 +00:00
Owner
Copy Link

Originally created by @WSLUser on GitHub (Jun 12, 2019).

Summary of the new feature/enhancement

Piggy backing off of https://github.com/microsoft/terminal/issues/867, I noticed the PR adding an About section in the menu. Now I'd like for a summary of Release Notes (could be a "What's New?" for each build once published to the Store. This could either be it's own clickable option in the menu or you could include a link on the bottom of the About section. But ideally it would act like VS Code. Since pictures are worth a thousand words, here's an example of how the About section could look if we aren't adding the Release Notes there (but note it does show the commit number and has a copy/paste option which would be helpful for filing issues):

image

Obviously some software shown isn't applicable, but the idea of it would be nice. For Release Notes itself, it could open up a json or html file showing the major changes and bug fixes similar to how extensions for VS Code work (Gitlens in particular comes to mind). (Sixel support here would go a long way if we want to display in the terminal itself). A helper link that went to the Github page showing all the applicable Pull requests that are associated with the release at the end of the Release Notes would be nice as well.

A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).

Creates transparency for users to know what's changed and makes it easier for filing issues. Ideally the Release Notes would be available to the local host so that Internet connection isn't required for users in Internet-restricted environments.

Proposed technical implementation details (optional)

Recommend using https://github.com/microsoft/terminal/pull/1196 as a base point/reference for the changes.

Originally created by @WSLUser on GitHub (Jun 12, 2019). # Summary of the new feature/enhancement Piggy backing off of https://github.com/microsoft/terminal/issues/867, I noticed the PR adding an About section in the menu. Now I'd like for a summary of Release Notes (could be a "What's New?" for each build once published to the Store. This could either be it's own clickable option in the menu or you could include a link on the bottom of the About section. But ideally it would act like VS Code. Since pictures are worth a thousand words, here's an example of how the About section could look if we aren't adding the Release Notes there (but note it does show the commit number and has a copy/paste option which would be helpful for filing issues): ![image](https://user-images.githubusercontent.com/33032910/59354024-c4f81b00-8d13-11e9-8d70-2098fec69d31.png) Obviously some software shown isn't applicable, but the idea of it would be nice. For Release Notes itself, it could open up a json or html file showing the major changes and bug fixes similar to how extensions for VS Code work (Gitlens in particular comes to mind). (Sixel support here would go a long way if we want to display in the terminal itself). A helper link that went to the Github page showing all the applicable Pull requests that are associated with the release at the end of the Release Notes would be nice as well. **A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable).** Creates transparency for users to know what's changed and makes it easier for filing issues. Ideally the Release Notes would be available to the local host so that Internet connection isn't required for users in Internet-restricted environments. **Proposed technical implementation details (optional)** Recommend using https://github.com/microsoft/terminal/pull/1196 as a base point/reference for the changes. <!-- A clear and concise description of what you want to happen. -->
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-UserInterface Help Wanted Issue-Feature Product-Terminal Resolution-Fix-Committed
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#1612
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?