The new Windows Terminal and the original Windows console host, all in the same place!
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 34%
Response Time: -
First Timer Success: 20%
microsoft/terminal has a recorded first-timer success rate of 20.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in microsoft/terminal respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 62.7 places microsoft/terminal in the A tier.
The external contributor pull request merge rate for microsoft/terminal is 34.0%, based on public PR activity from non-core contributors.
microsoft/terminal currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in microsoft/terminal.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/microsoft/terminal?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (43% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Windows Terminal version 1.24.11911.0 Windows build number 10.0.26200.0 Other Software No response Steps to reproduce Paste this character in the terminal (I've tried powershell and wsl/ubuntu): 1️⃣ Alternatively, create a directory or file with that in the same and ls to see it rendered (I originally ran across it in a directory name). Expected Behavior Renders as a number in a box. Actual Behavior The number and box are not aligned, so the right edge of the box goes through the number. Here are some examples:
Windows Terminal version 1.24.11911.0 (stable), also 1.25.1912.0 (Preview), and a local Dev build of current main Windows build number 10.0.26200.9168 Other Software Reproduced with ordinary PowerShell / cmd panes (no special client). Machine: Intel Core Ultra 5 225H, 32 GB RAM. I already have a fix and will send a PR against this issue. Steps to reproduce Open Windows Terminal (stable is enough; Debug Dev builds make it much worse). Split the tab into 4 panes (Alt+Shift++ / Alt+Shift+-). Focus a pane and hold Alt+Shift+Left or Alt+Shift+Right for a couple of seconds. Repeat while the terminals have a typical amount of scrollback / output. Expected Behavior The splitter should keep moving while the key is held, and the window should stay responsive. Releasing the key should stop the splitter immediately. Actual Behavior Keyboard auto-repeat is ~30 Hz. Each resizePane currently calls _CreateRowColDefinitions() immediately, which forces a XAML grid relayout and a reflow of every termin
Windows Terminal version 1.24.11911.0 Windows build number Windows 11 25H2, Build 26200.8875 Other Software Shell: PowerShell 7.6.4 IME: Microsoft Pinyin (new version, TSF3, NOT compatibility mode) Steps to reproduce Use Windows 11 25H2 (Build 26200) with the latest Windows updates (KB5100998, KB5101650, KB5120102 installed on 2025-07-25) Ensure Microsoft Pinyin IME is using the new version (NOT enabled "Use previous version of Microsoft Pinyin IME" compatibility mode) Open Windows Terminal (any profile, e.g. PowerShell) Press Shift (or Ctrl+Space) to switch to Chinese input mode Expected Behavior IME switches to Chinese input mode. Candidate/composition UI appears. Can type Chinese characters. Actual Behavior Shift key (and other IME switch shortcuts) have no effect. IME stays in English mode. Can only type English letters. Chinese input works fine in all non-terminal apps (Notepad, browser, etc.). Workaround Enable "Use previous version of Microsoft Pinyin IME" in Windows Setting
Description of the new feature At the moment, "Position of newly created tabs" allows "After the last tab" and "After the current tab". I prefer "After the last tab". However, when duplicating the current tab (expressly with "Duplicate tab", Ctrl+Shift+d), I find myself almost always dragging the new tab next to its original. It would be nice to have an intermediate setting (e.g. "After last except duplicates") that would behave like "After last", except it would behave like "After current" for tabs created with "Duplicate tab". Proposed technical implementation details Implementing this would likely require that the information of whether the new tab creation was requested with the "Duplicate tab" command (and not e.g. by selecting the same profile again) survives to the point when the tab's location is decided.
Windows Terminal version 1.24.11321.0 Windows build number 10.0.19045 Other Software Virtual desktops (native) Steps to reproduce Add the following action to settings.json: { "command": { "action": "globalSummon", "desktop": "toCurrent", "monitor": "any", "toggleVisibility": false }, "id": "User.MyGlobalSummon." } Set the keybinding for "Show/Hide the Terminal window". I'm using win+~ (replacing quake mode). Move a Terminal window to a particular virtual desktop and monitor. Switch to any virtual desktop and move an application window to the foreground on any monitor BUT the MRU Terminal window's monitor. Run the keyboard shortcut. Expected Behavior The MRU Terminal window moves to the current virtual desktop and is left where it is/was on the monitor. Actual Behavior The MRU Terminal window moves to the current virtual desktop and the monitor with the currently foregrounded window.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to microsoft/terminal, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of microsoft/terminal acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 34.0% were successfully merged into the primary branch.
microsoft/terminal has a recorded first-timer success rate of 20.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 62.7 places microsoft/terminal in the Welcoming tier.
The external pull request merge rate is 34.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, microsoft/terminal currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for microsoft/terminal are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.