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

Windows Terminal (Dev Build) should display version as git commit instead of "0.1.0.0" #3908

New Issue
Open
opened 2026-01-30 23:33:01 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:33:01 +00:00
Owner
Copy Link

Originally created by @darthpale on GitHub (Sep 17, 2019).

Environment

Windows build number:Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0 
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Build from cloned git tree.
git clone https://github.com/microsoft/Terminal.git
Build x64 release (or debug)
Deploy solution.
Click the menu down arrow
choose "About"

Expected behavior

Version is reported as at least 0.4
Since that is was is referenced in https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-4-release/

Actual behavior

About box displays
Windows Terminal (Dev Build)
Version: 0.0.1.0

Additional Info

Other git repositories auto update release info to include git commit ID in the about box if built from a clone of the repository. In addition to keeping the version reported in git clone builds up to date with what you have in the Microsoft store you might consider putting the git commit string in the version string and stripped out on release.

Originally created by @darthpale on GitHub (Sep 17, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number:Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce Build from cloned git tree. git clone https://github.com/microsoft/Terminal.git Build x64 release (or debug) Deploy solution. Click the menu down arrow choose "About" <!-- A description of how to trigger this bug. --> # Expected behavior Version is reported as at least 0.4 Since that is was is referenced in https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-4-release/ <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior About box displays Windows Terminal (Dev Build) Version: 0.0.1.0 <!-- What's actually happening? --> # Additional Info Other git repositories auto update release info to include git commit ID in the about box if built from a clone of the repository. In addition to keeping the version reported in git clone builds up to date with what you have in the Microsoft store you might consider putting the git commit string in the version string and stripped out on release.
claunia added the Help WantedIssue-TaskProduct-TerminalArea-UserInterface labels 2026-01-30 23:33:02 +00:00
claunia commented 2026-01-30 23:33:03 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 17, 2019):

I had actually requested this before in my About version issue but it was closed once we had a version put there. I think we should have a commit id even when it's installed from the Store just like VS Code (minus the Store part since they still haven't bothered to do it even though they created a snap package). That commit id will let everyone know, hey everything up to this point works this certain way. Especially useful for regressions or new bugs cropping up.

@WSLUser commented on GitHub (Sep 17, 2019): I had actually requested this before in my About version issue but it was closed once we had a version put there. I think we should have a commit id even when it's installed from the Store just like VS Code (minus the Store part since they still haven't bothered to do it even though they created a snap package). That commit id will let everyone know, hey everything up to this point works this certain way. Especially useful for regressions or new bugs cropping up.
claunia commented 2026-01-30 23:33:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 1, 2024):

You know, we had more thoughts on this over in #16792. Basically, stamping the git commit into the source code for dev builds seems overall, kinda annoying. That'll cause at least one header to change every time you make a git commit, which means re-building possibly a bunch of projects just because you committed.

But, I do think we can stick the commit in the code reasonably for non-dev builds. That'll let us refer to the specific commit for stable, preview, and canary builds.

I think I'm inclined to close this out in favor of that route instead.

@zadjii-msft commented on GitHub (Mar 1, 2024): You know, we had more thoughts on this over in #16792. Basically, stamping the git commit into the source code for dev builds seems overall, kinda annoying. That'll cause at least one header to change every time you make a git commit, which means re-building possibly a bunch of projects just because you committed. But, I do think we can stick the commit in the code reasonably for non-dev builds. That'll let us refer to the specific commit for stable, preview, and canary builds. I think I'm inclined to close this out in favor of that route instead.
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-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#3908
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?